2.3. Running the Installation

To run the downloaded packages differs depending on the download method. This section will now detail how to run the installation for a RHN download and CSP download.

2.3.1. Running a RPM Installation

Running Tomcat version 5 or 6
Tomcat can be started, stopped, and configured to start automatically at boot time either from the command line or using a graphical tool.
The tomcat5 or tomcat6 services can be started and stopped using the service command as root on a console window (as is typical of a network service):
Starting and stopping the tomcat5 service:
service tomcat5 start
service tomcat5 stop
Starting and stopping the tomcat6 service:
service tomcat6 start
service tomcat6 stop
Once the tomcat service has been started, you can verify that it is running by pointing your web browser to http://localhost:8080.
The tomcat service runs under a new tomcat system user. Due to file system permissions it may be necessary to use the su -s /bin/bash tomcat system command to deploy the application under the webapps directory. Alternatively, a developer can be listed in the tomcat user group by the system administrator. The best approach is to use the Web Console (URL above) to deploy the application.
The behavior at boot can be controlled with the chkconfig command (see the chkconfig man page for further details).
Configuration can then be altered in the /etc/sysconfig/tomcat5 file for Tomcat version 5 and the /etc/sysconfig/tomcat6 file for Tomcat version 6.
Running the HTTP Server
The HTTP Server can be started, stopped, and configured to start automatically at boot time either from the command line or using a graphical tool.
The following examples of running the HTTP Server will also cover the differences of undertaking this on Red Hat Enterprise Linux 4 and 5
You can start and stop the HTTP Server service using the service command as root on a console window (as is typical of a network service):
Starting and stopping the HTTP Server service on Red Hat Enterprise Linux 4:
service httpd22 start
service httpd22 stop
Starting and stopping the HTTP Server service on Red Hat Enterprise Linux 5:
service httpd start
service httpd stop
Configuration can then be altered in the /etc/sysconfig/httpd22 file on Red Hat Enterprise Linux 4 and the /etc/sysconfig/httpd file on Red Hat Enterprise Linux 5.
Running the mod_jk
To load the mod_jk module, the file /etc/httpd22/conf/httpd.conf on Red Hat Enterprise Linux 4 or the file /etc/httpd/conf/httpd.conf on Red Hat Enterprise Linux 5 needs to be updated, and a workers.properties file needs to be added in that directory. See /usr/share/doc/mod_jk-ap20-1.2.28/mod_jk.conf.sample and /usr/share/doc/mod_jk-ap20-1.2.28/workers.properties.sample for examples of how this can be achieved.
Running log4j for logging in Tomcat 6
To use log4j for logging in Tomcat 6, install the tomcat6-log4j rpm file.
Running log4j for logging in Tomcat 5
To use log4j for logging in Tomcat 5, you must copy the appropriate files from the Tomcat 6 distribution included in JBoss Enterprise Application Platform 1.0.1. Copy log4j.jar from tomcat6/extras into tomcat5/common/lib. Copy log4j.properties from tomcat6/extras files into tomcat5/common/classes.
Running Apache Tomcat Native
Edit /etc/sysconfig/tomcat5 file for Tomcat 5 or /etc/sysconfig/tomcat6 for Tomcat 6 and add the LD_LIBRARY_PATH variable so that it points to the library correct library:
The correct value when running on 64bit architecture is:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64/
The correct value when running on 32bit architecture is:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/