2.2. ZIP Installation

Procedure 2.4. Downloading JBoss Web Server

1. Open a browser and log in to the Customer Portal at http://access.redhat.com.
2. Click Downloads.
3. Click Red Hat JBoss Web Server in the Product Downloads list.
4. Select the correct JBoss Web Server version from the Version drop-down menu.
5. Click Download for each of the following files, ensuring that you select the correct platform and architecture for your system:

   • Red Hat JBoss Web Server 3.0 Application Server (jws-application-servers-3.0.0-<platform>-<architecture>.zip)
   • Red Hat JBoss Web Server 3.0 Apache HTTP Server (jws-httpd-3.0.0-<platform>-<architecture>.zip)

Procedure 2.5. Extract JBoss Web Server

• Unzip the downloaded ZIP files to your installation directory.

  Note

  We recommend that you install JBoss Web Server in the /opt/ directory.

Procedure 2.6. Setting the JAVA_HOME Environment Variable

• In the bin directory of Tomcat (either JWS_HOME/tomcat7/bin or JWS_HOME/tomcat8/bin), create a file named setenv.sh, and insert the JAVA_HOME path definition.
  For example: export JAVA_HOME=/usr/lib/jvm/jre-1.7.0-openjdk.x86_64

Procedure 2.7. Creating a Tomcat User

1. In a shell prompt as the root user, change directory to JWS_HOME.
2. Run the following command to create the tomcat user group:

   # groupadd -g 91 -r tomcat

3. 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

4. From JWS_HOME, run the following command to assign the ownership of the Tomcat directories to the tomcat user to allow the user to run the Tomcat service:

   # chown -R tomcat:tomcat tomcat<VERSION>

   Replace <VERSION> with the respective Tomcat version number (7 or 8).
   You can use ls -l to verify that the tomcat user is the owner of the directory.
5. Ensure that the tomcat user has execute permissions to all parent directories. For example:

   # chmod -R u+X tomcat<VERSION>

Procedure 2.8. Creating an Apache User

1. In a shell prompt as the root user, change directory to JWS_HOME.
2. Run the following command to create the apache user group:

   # groupadd -g 48 -r apache

3. 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

4. From JWS_HOME, run the following command to assign the ownership of the Apache directories to the apache user to allow the user to run httpd:

   # chown -R apache:apache httpd

   You can use ls -l to verify that the apache user is the owner of the directory.

Procedure 2.9. Removing/Re-Adding SSL Support

• Go to the JWS_HOME/httpd/conf.d/ directory and 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. Enabling log4j Logging for Tomcat

1. Open a shell prompt and change directory to JWS_HOME/extras/.
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 (7 or 8).
3. Replace tomcat-juli.jar file in your Tomcat bin directory with the tomcat-juli.jar file from JWS_HOME/extras/:

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

Procedure 2.11. Configuring mod_jk

1. In JWS_HOME/httpd/conf.d/, create a file named workers.properties.
   This file should contain the available workers (JBoss instances).
2. In JWS_HOME/httpd/conf.d/, create a file named mod_jk.conf.
   This file contains general mod_jk configuration.
3. In JWS_HOME/httpd/conf.d/, create a file named uriworkermap.properties.
   This file contains request mapping rules that map requests to workers.

Procedure 2.12. Configuring mod_cluster

• mod_cluster can be configured in JWS_HOME/httpd/conf.d/mod_cluster.conf.
  For more information about customizing mod_cluster, see the mod_cluster Connector section of the HTTP Connectors and Load Balancing Guide.

Procedure 2.13. Running the Apache HTTP Server Post-Installation Script

1. In a shell prompt as the root user, change directory to JWS_HOME/httpd.
2. Run the following command:

   # ./.postinstall

Procedure 2.14. Starting Tomcat

• Run the following command as the tomcat user with your respective Tomcat version (7 or 8):

  $ sh JWS_HOME/tomcat<VERSION>/bin/startup.sh

  Important

  Although there are multiple methods of starting Tomcat, it is recommended that you use the startup.sh script. To start Tomcat as a service using Jsvc, see Chapter 5, Using Jsvc to Start Tomcat.

Procedure 2.15. Starting Apache HTTP Server

• To start Apache HTTP Server (httpd), in a terminal as the root, change to JWS_HOME/httpd/sbin/ and run the following command:

  # ./apachectl start

Procedure 2.16. Stopping Tomcat

• To stop Tomcat, run the following command as the root user with your respective Tomcat version (7 or 8):

  # sh JWS_HOME/tomcat<VERSION>/bin/shutdown.sh

Procedure 2.17. Stopping Apache HTTP Server

• To stop Apache HTTP Server (httpd), in a shell prompt as the root user change to JWS_HOME/httpd/sbin/, and run the following command:

  # ./apachectl stop