Red Hat Training
A Red Hat training course is available for Red Hat JBoss Web Server
3.3.4. Configuring the Environment
Before running JBoss Enterprise Web Server, you can optionally configure environment:
- remove SSL (refer to Procedure 3.16, “Removing SSL”);
- add log4j logging (refer to Procedure 3.18, “Removing log4j From Tomcat 6”);
- enable mod_jk or mod_cluster (refer to Procedure 3.20, “Configuring mod_jk” and Procedure 3.21, “Configuring mod_cluster”)
Procedure 3.16. Removing SSL
The SSL support is optional. It is provided by the mod_ssl package and is enabled on package installation. To remove SSL, do the following:
- At the shell prompt, become the root user.
- Run the respective uninstall command:
- on Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 5:
# yum remove mod_ssl
- on Red Hat Enterprise Linux 4:
# rpm -e mod_ssl22
Configuring log4j
For tomcat6, the log4j support is provided by the tomcat6-log4j package and is enabled on package installation (refer to Procedure 3.15, “Installing Enterprise Web Server from RPM Packages”). To enable log4j on tomcat5, copy the respective log4j resources from the tomcat6
to the tomcat5
directory (refer to Procedure 3.17, “Adding log4j on tomcat5”)
Procedure 3.17. Adding log4j on tomcat5
- Install the
tomcat6-log4j
RPM package. - From
/usr/share/java/tomcat6/
, copy:log4j.jar
to/usr/share/tomcat5/common/lib
andlog4j.properties
to/usr/share/tomcat5/common/classes
.
Procedure 3.18. Removing log4j From Tomcat 6
Follow this procedure to remove log4j from Tomcat 6:
- At the shell prompt, become the root user.
- Run the respective uninstall command:
- on Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 5:
# yum remove tomcat6-log4j
- on Red Hat Enterprise Linux 4:
# rpm -e tomcat6-log4j
Procedure 3.19. Removing log4j From Tomcat 5
Follow this procedure to remove log4j from Tomcat 5
- Remove the
log4j.jar
file from the/usr/share/tomcat5/common/lib
directory. - Remove the
log4j.properties
file from the/usr/share/tomcat5/common/classes
directory.
Procedure 3.20. Configuring mod_jk
Follow this procedure to configure and enable mod_jk:
- Install the template
mod_jk
configuration file:# cp /usr/share/doc/mod_jk-ap20-*/mod_jk.conf.sample /etc/httpd/conf.d/mod_jk.conf
- Install the template
workers.properties
file:# cp /usr/share/doc/mod_jk-ap20-*/workers.properties.sample /etc/httpd/conf/workers.properties
- Add worker mappings to
workers.properties
. For example:# Mount the Servlet context to the ajp20 worker /jmx-console=loadbalancer /jmx-console/*=loadbalancer /web-console=loadbalancer /web-console/*=loadbalancer
Note
The default configuration is adequate for low-traffic web sites. For optimization information for moderate and high-load web sites, refer to http://kbase.redhat.com/faq/docs/DOC-15836.
Procedure 3.21. Configuring mod_cluster
The mod_cluster load balancer is optional. It is provided by the mod_cluster package and is enabled on package installation.
Follow this procedure to configure the HTTP Server to use mod_cluster as its load balancer:
- In the
/etc/httpd/conf/httpd.conf
file, add the hash (#
) sign at the beginning of the following line to disable mod_proxy_balancer.so:LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
This module is incompatible with the JBoss HTTP Connector. - Configure the server to load the JBoss HTTP Connector modules:
- Create the file
/etc/httpd/conf.d/JBoss_HTTP.conf
. - Add the following lines to the
JBoss_HTTP.conf
file:LoadModule slotmem_module modules/mod_slotmem.so LoadModule manager_module modules/mod_manager.so LoadModule proxy_cluster_module modules/mod_proxy_cluster.so LoadModule advertise_module modules/mod_advertise.so