4.4. Configuring the Environment


After you have installed JBoss Enterprise Web Server, set the JAVA_HOME for your Tomcat (refer to Procedure 4.4, “Configuring Tomcat”).
Optionally, you can also:

Procedure 4.4. Configuring Tomcat

Before starting Tomcat, set its JAVA_HOME variable to point to a supported JDK (1.6.0):
  1. Locate the tomcat configuration file:
    • For Tomcat 7: /opt/jboss-ews-2.0/etc/sysconfig/tomcat7
    • For Tomcat 6: /opt/jboss-ews-2.0/etc/sysconfig/tomcat6
  2. Open the configuration file and delete the hash (#) sign at the beginning of the following line:
    # JAVA_HOME="/usr/java"

Procedure 4.5. Removing SSL

JBoss Enterprise Web Server by default supports SSL. However, you may remove the SSL support.
Follow this procedure to remove or add SSL:
  1. Go to /opt/jboss-ews-2.0/etc/httpd/conf.d
  2. Rename the SSL configuration file:
    • To remove SSL, rename ssl.conf to ssl.conf.disabled.
    • To re-enable the SSL, rename ssl.conf.disabled to ssl.conf.

Procedure 4.6. Configuring log4j

Follow this procedure to add log4j logging to Tomcat:
  1. Go to the /opt/jboss-ews-2.0/share/extras directory.
  2. Copy the log4j.jar and log4j.properties files to the lib directory of the Tomcat directory:
    • If using Tomcat 6, run the following commands:
      extras]# cp log4j.properties ../tomcat6/lib/
      extras]# cp log4j.jar ../tomcat6/lib/
    • If using Tomcat 7, run the following commands:
      extras]# cp log4j.properties ../tomcat7/lib/
      extras]# cp log4j.jar ../tomcat7/lib/

Procedure 4.7. Configuring mod_jk

To configure the HTTP Server to use mod_jk, define the following:
  • available workers (JBoss instances) in the workers.properties file
  • the mod_jk configuration file mod_jk.conf
Follow this procedure to configure the HTTP Server to use mod_jk as its load balancer:
  1. Create a workers.properties file in /opt/jboss-ews-2.0/etc/httpd/conf (refer to http://tomcat.apache.org/connectors-doc/reference/workers.html).
  2. Create a mod_jk.conf in /opt/jboss-ews-2.0/etc/httpd/conf.d/, (refer to http://tomcat.apache.org/connectors-doc/reference/apache.html).

    Note

    You can also copy and modify the sample files mod_jk.conf.sample and workers.properties.sample available in /opt/jboss-ews-2.0/etc/httpd/conf/: modify their content as needed and rename them to mod_jk.conf and workers.properties.

Procedure 4.8. Configuring mod_cluster

  1. Mod_cluster is part of the JBoss Enterprise Web Server 2.0 installation.
  2. In /opt/jboss-ews-2.0/httpd/conf/httpd.conf add a hash (#) sign at the beginning of the following line to disable the mod_proxy_balancer module:
    LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    This module is incompatible with the JBoss HTTP Connector.
  3. Configure the server to load the JBoss HTTP Connector modules:
    1. Create the file /opt/jboss-ews-2.0/httpd/conf.d/mod_cluster-native.conf.
    2. Add the following lines to the file /opt/jboss-ews-2.0/httpd/conf.d/mod_cluster-native.conf:
      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
      
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top