3.2.2. Configuring the Environment

Before running JBoss Enterprise Web Server, the JAVA_HOME variable needs to be set (refer to Procedure 3.6, “Setting JAVA_HOME”).
Optionally, you can also:
Run the post-installation script once you have set up the environment (refer to Procedure 3.13, “Running the Post-Installation Script”).

Procedure 3.6. Setting JAVA_HOME

Follow this procedure to set the JAVA_HOME variable of your Tomcat to point to a supported Java:
  1. In the bin directory of your Tomcat (either $EWS_HOME/tomcat5/bin or $EWS_HOME/tomcat6/bin), create the setenv.sh file (for example, issue the command vim tomcat<VERSION>/bin/setenv.sh).
  2. Add the JAVA_HOME path definition into the file; for example export JAVA_HOME=/usr/lib/jvm/jre-1.6.0-openjdk.x86_64

Procedure 3.7. Creating tomcat User

Follow this procedure to create the tomcat user and its parent group:
  1. At the shell prompt, become the root user.
  2. Run the following command to create the tomcat user group:
    # groupadd -g 91 -r tomcat
  3. Go to $EWS_HOME.
  4. From $EWS_HOME, run the following command to create the tomcat user in the tomcat user group:
    # useradd -c "Tomcat" -u 91 -g tomcat -s /bin/sh -r -d /home/tomcat tomcat
  5. From $EWS_HOME, run the following command to assign the ownership of the tomcat directories to the tomcat user and allow the user to run the tomcat service:
    # chown -R tomcat:tomcat tomcat<VERSION> 
    Substitute <VERSION> with the respective tomcat version number (5 or 6).
  6. From $EWS_HOME, issue the command ls -l and check if the tomcat user is the owner of the Tomcat directory.
  7. Make sure that the tomcat user has the execution permission to all parent directories.

Procedure 3.8. Setting the apache User

Follow this procedure to set up the apache user:
  1. Run the following commands as the root user to create the apache user group:
    # groupadd -g 48 -r apache
  2. Run the following command to create the apache user in the apache user group:
    # useradd -c "Apache" -u 48 -g apache -s /bin/sh -r -d /home/apache apache
  3. Change to $EWS_HOME and run the following command to assign the ownership of the apache directories to the apache user and allow the user to run httpd:
    # chown -R apache:apache httpd
  4. From $EWS_HOME, issue the command ls -l and check that the apache user has execution permission to the respective Apache install path. Output is similar to the following:
    drwxrwxr-- 11 apache apache 4096 Feb 14 06:52 httpd

Procedure 3.9. Removing SSL

JBoss Enterprise Web Server supports SSL by default, but it can be removed.
Follow this procedure to remove or re-add SSL:
  1. Go to the $EWS_HOME/httpd/conf.d/ directory.
  2. Rename the SSL configuration file:
    • To remove SSL, rename ssl.conf to ssl.conf.disabled.
    • To re-add SSL, rename ssl.conf.disabled to ssl.conf.

Procedure 3.10. Configuring log4j

Follow this procedure to add log4j logging to Tomcat:
  1. Go to the $EWS_HOME/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.jar log4j.properties ../tomcat6/lib
      extras]# cp tomcat-juli-adapters.jar $EWS_HOME/tomcat6/lib
    • If using Tomcat 5, run the following commands:
      extras]# cp log4j.properties ../tomcat5/common/classes
      extras]# cp log4j.jar ../tomcat5/common/lib

Procedure 3.11. 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
Follow this procedure to configure the HTTP Server to use mod_jk as its load balancer:
  1. In the $EWS_HOME/httpd/conf/ directory, create workers.properties
  2. In the $EWS_HOME/httpd/conf.d/ directory, create mod_jk.conf.

    Configuration Samples

    You can also use the template files from the jboss-ews-docs-1.0.2.zip file (the file is available at the Red Hat Customer Portal ): after you have downloaded and unzipped the file, copy the sample files mod_jk.conf.sample and workers.properties.sample from the $EWS_HOME/doc/mod_jk/ to the locations defined in Step 1 and Step 2. Rename them (drop the sample extension) and modify their content as needed (to refer to Section 3.2.6, “Additional Resources”).

Procedure 3.12. Configuring mod_cluster

Follow this procedure to configure the HTTP Server to use mod_cluster as its load balancer:
  1. In the <EWS_HOME>/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.
  2. Configure the server to load the JBoss HTTP Connector modules:
    1. In the $EWS_HOME/httpd/conf.d/ directory, create the JBoss_HTTP.conf file.
    2. 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

Procedure 3.13. Running the Post-Installation Script

Follow this procedure to run the post-installation script:
  1. At the shell prompt, become the root user.
  2. Change to the /opt/jboss-ews-2.0/httpd directory.
  3. Run the following command:
    # ./.postinstall

    Note

    The system uses the /opt directory as a default directory for installing JBoss Enterprise Web Server. Make sure the /opt directory is present during installation.