2.4.2. Configuring the Environment

Procedure 2.6. Setting JAVA_HOME

1. In the bin directory of your Tomcat (either $EWS_HOME/tomcat6/bin or $EWS_HOME/tomcat7/bin), create the setenv.sh file.
   For example, run 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 2.7. Creating tomcat User

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 /opt/jboss-ews-2.1.
4. From /opt/jboss-ews-2.1, 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 tomcat

5. From /opt/jboss-ews-2.1, 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 (6 or 7).
6. From /opt/jboss-ews-2.1, 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 2.8. Setting 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 apache

3. Change to /opt/jboss-ews-2.1 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 /opt/jboss-ews-2.1, 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 2.9. Removing SSL

1. Go to the /opt/jboss-ews-2.1/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 2.10. Configuring log4j

1. Go to the /opt/jboss-ews-2.1/extras/ directory.
2. Copy the log4j-eap6.jar, log4j.properties, and tomcat-juli-adapters.jar files to the lib directory of the Tomcat directory.
   For example:

   # cp log4j.properties ../tomcat<VERSION>/lib/

   # cp log4j-eap6.jar ../tomcat<VERSION>/lib/

   # cp tomcat-juli-adapters.jar ../tomcat<VERSION>/lib/

   Replace <VERSION> with the respective Tomcat version number (6 or 7).
3. Replace tomcat-juli.jar file in your Tomcat bin directory with the tomcat-juli.jar file from /opt/jboss-ews-2.1/extras/:

   # cp tomcat-juli.jar ../tomcat<VERSION>/bin/

Procedure 2.11. Configuring mod_jk

1. In the /opt/jboss-ews-2.1/httpd/conf/ directory, create workers.properties.
2. In the /opt/jboss-ews-2.1/httpd/conf.d/ directory, create mod_jk.conf.

   Note

   You can also use the template files from the jboss-ews-docs-2.1.0.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 /opt/jboss-ews-2.1/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 (see Section 2.4.7, “Additional Resources”).

Procedure 2.12. Configuring mod_cluster

• The mod_cluster configuration can be customized in /opt/jboss-ews-2.1/httpd/conf.d/mod_cluster.conf.
  For more information about customizing mod_cluster, see the JBoss HTTP Connector section of the HTTP Connectors and Load Balancing Guide.

Procedure 2.13. Running the Post-Installation Script

1. At the shell prompt, become the root user.
2. Change to the /opt/jboss-ews-2.1/httpd directory.
3. Run the following command:

   # ./.postinstall