Apache Tomcat Installation_English

							 Apache Tomcat / J-Guar
Setup/License Installation
            Logo
         Mayıs, 2012
Apache Tomcat Installation
It is a must to download the supported version of Apache Tomcat (the most recent version of Tomcat 6
family) in order to use JGuar product on Apache Tomcat application server. You can get Apache Tomcat
application server via Tomcat’s website (http://tomcat.apache.org/download-60.cgi) or partner ftp page.
Tomcat 6 application server can be installed in two methods:

Installation with .zip extension
If you install the file with “.zip” extension, it will be enough for you to open it in the required directory where
you will install Tomcat in your device. When you install the application in this method, it will be ready to run
over the relevant directory after opening .zip file. The content of this directory will be as shown below:




You will see files with “.bat” extension in bin folder that will be used to run and terminate Tomcat
application.




While startup.bat file starts the server, shutdown.bat file stops the running server.
Installation with .exe extension
If you install the file with “.exe” extension, you must run this file. This file starts a wizard that will install
Tomcat into Windows Operating System as an application. By following the steps you will install Tomcat
application server on your device. Tomcat application server is installed as a Windows Service if this method
is followed, and it is listed in Control Panel > Administrative Tools > Services page:




In order to run and stop this Tomcat server, Service file that is listed must be started and stopped. Thereby
Apache Tomcat is installed in C:\Program Files (x86)\Apache Software Foundation\Tomcat 6.0 directory.

Apache Tomcat Settings
Defining User for the Application Manager
The user definitions required to use the application manager are not available when Apache Tomcat is first
installed. This definition must be written initially. In order to do so, tomcat-users.xml file located in conf
directory of Apache installation directory is opened, and the following information is written in:

<?xml version='1.0' encoding='utf-8'?>

<tomcat-users>

  <role rolename="manager"/>

  <role rolename="admin"/>

  <user username="admin"password="logo" roles="admin,manager"/>


</tomcat-users>


A user whose user name is admin and password is logo is defined in the yellow line. This user is assigned
admin and manager roles, so Tomcat’s application manager becomes active for this user. After this
adjustment, Tomcat server must be restarted if it is running.
JVM and Memory Settings
Settings for Tomcat with zip extension
JVM which will be used by Apache Tomcat server is determined by JAVA_HOME or JRE_HOME variants
defined in the device. If these two variants are not defined in the device, one of them must be defined. If
these variants cannot be defined in the device for any reason (it might affect another application on the
same device), these definitions must be added to startup.bat file located in bin folder of Tomcat.




In order to run JGuar application properly on this server, server memory settings must be done. The
following line is added to startup.bat file for memory settings:

set JAVA_OPTS=-Xmx1024M -Xms512M -XX:PermSize=256m

After making these settings, Tomcat server must be restarted if it is running.

Settings for Tomcat with .exe extension
JVM which will be used by Tomcat server is selected while installing the application with a setup wizard, and
then Tomcat works with the selected JVM. Therefore, you won’t need to set a JVM manually for a Tomcat
server installed in this method. However, in order to run JGuar application properly in this Tomcat server,
JVM memory settings must be done. Find Apache Tomcat 6.0 folder from Start menu and select
Configure Tomcat menu option in this folder.
If you cannot find this option in Start menu, then run tomcat6w.exe file located in bin folder in Tomcat
installation directory. Open Java tab in this window and then set memory options located at the bottom of
this window as required:




You must enter the value shown in the picture above (-XX:PermSize=256m) in Java Options section. After
making these settings, Tomcat server must be restarted if it is running.
EAR Installation on Tomcat
After performing the above mentioned settings on Tomcat server, the product can be installed by EAR file.
In order to install the product on Tomcat, Tomcat server is opened and “http://localhost:8080” address is
called via a web browser. If it does not work, it means that either Tomcat server has not been started
properly or a problem may have occurred during the installation. The relevant page that is called will be as
below:




Tomcat Manager link located at the left (shown above) is clicked. When clicked, a user name – password
window prompts to open the manager application. User name and password defined in tomcat-users.xml
file are entered inhere. (Our user name and password example is admin – logo in this document.) If user
name and password are confirmed, Tomcat application manager opens.
Applications installed on the server are listed in Application Manager. If JGuar application is installed, it will
appear in this list. JGuar application can be stopped and restarted from this list when required. In order to
install the product ear on Tomcat server, you must open ear file and then take “.war” file. Tomcat
application server does not work over ear file directly. An archive manager program such as Win zip or Win
rar can be used to open ear file.

After opening EAR file by an archive manager program, the file with “.war” extension must be extracted to
the device. Then this war file is selected under “WAR file to deploy” heading in Deploy section of Tomcat
application manager and “Deploy” button is clicked.




If the product is installed successfully, it will appear in the applications list at the top of this page. This
product is located in webapps folder of Tomcat application.




Logs of Tomcat server are located in logs folder under Tomcat directory. “localhost****.log “ file keeps the
logs of the applications on server (and the product’s as well).
Settings and Operations After Installing
First of all the connection between the Application and Database must be established after installing by
means of jSAdmin.jsp segment. The required address is http://localhost:8080/logo/jSAdmin.jsp.

While entering this section of the application, user name and password are LOGO/LOGO.
After opening this page, “Add” button is clicked to add a new connection setting. The required information is
entered and saved. After saving, “Test” button is clicked, and the connection is checked.

Connection page looks like below:




Note 1: Server name field can be filled as your SQL Server name or localhost.
Note 2: JTDS parameter must be activated in case that you are using Microsoft SQL 2008. This operation
must be performed over “Server Configuration Settings Organizer.”
Note 3: In Server Configuration Settings Organizer      , Client Optimization/ Optimized Resource Version
information must also be entered according to the version number in use and then activated.

Note 4: In order to activate all changes made in Server Configuration Settings Organizer        Application
Server service must be stopped and restarted.




After testing the connection successfully, Application Server must be stopped and restarted again.

After opening the service, http://localhost:8080/logo/jSAdmin.jsp is called and the following transactions
located under Database Operations are performed respectfully.

Generate/Upgrade System Tables
Generate/Upgrade Reference Counting Tools of System Tables

After performing this transaction, company must call http://localhost:8080/logo/jAdmin.jsp address to
perform authorization and other system settings.

User name and password that will be entered in this page are admin and logo.

After making the required company, authorization etc definitions, use the following links to open the
application.
http://localhost:8080/logo/RunApp or
http://localhost:8080/logo/jGuar.jsp

User name and password that will be entered in this page are admin and logo.
Switching Debug Options On/Off

Debug options will be displayed as default after installing the application. In order to switch off this option,
“Debug.xml” file located under ....\apache-tomcat-6.0.32\webapps\logo\Config\System is edited and all
“true” parameters are changed to “false”. Logging level must be left empty instead of 7.



Web Application Status
Another program area where you’ll be able to track the current settings:
http://localhost:8080/logo/Status

You can track Application Info, Debug Options, Server and Client Variables, Form BuildOptions (not
required), Sessions status inhere. All settings performed on Debug Options will be valid until the Application
Server is stopped and started. Then it will return to the previous settings.




Warning 1  The above mentioned operations must be performed again after upgrading a new version.
Therefore you must take a back-up of DbConnection.xml file before upgrading. Then you can copy this file
to the same directory.



License Installation Transactions
The application must be activated by using License Keys delivered by LOGO after completing the
installation. (Since the product’s new versions must be installed initially, it must be activated by the
relevant license key after each installation.)

Activation Process

Activation must be performed over http://localhost:8080/logo/Activation address. In order to complete
activation process properly, internet connection is required. Language selection is the first step of activation
process. After that you can continue with the process in accordance with the instructions.
License keys delivered by Logo are entered and the process continues.




You will need reseller user, reseller password and user password for the activation process. In order to
maintain activation process, this information must be prepared.
*** After activation process, license key added over Administration group in Admin > Group Definitions
window must be selected to the group. Similarly, as new groups are added, this license key must be selected
to the newly defined groups as well.




When you receive License Renewal Warning, you must renew your license via the following address:
http://localhost:8080/logo/LicenseRenewal