Red Hat SummitDieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
2.3. Running the Installation
2.3.1. Running a RPM Installation
Tomcat can be started, stopped, and configured to start automatically at boot time either from the command line or using a graphical tool.
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):
tomcat5 service:
service tomcat5 start
service tomcat5 start
service tomcat5 stop
service tomcat5 stop
tomcat6 service:
service tomcat6 start
service tomcat6 start
service tomcat6 stop
service tomcat6 stop
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.
chkconfig command (see the chkconfig man page for further details).
/etc/sysconfig/tomcat5 file for Tomcat version 5 and the /etc/sysconfig/tomcat6 file for Tomcat version 6.
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.
service command as root on a console window (as is typical of a network service):
service httpd22 start
service httpd22 start
service httpd22 stop
service httpd22 stop
service httpd start
service httpd start
service httpd stop
service httpd stop
/etc/sysconfig/httpd22 file on Red Hat Enterprise Linux 4 and the /etc/sysconfig/httpd file on Red Hat Enterprise Linux 5.
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.
To use log4j for logging in Tomcat 6, install the tomcat6-log4j rpm file.
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.
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:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64/
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64/LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}