Procedure 2.1. Removing tomcatjss Package

1. At the shell prompt, become the root user.
2. Run the following uninstall command:

   # yum remove tomcatjss

Procedure 2.2. Installing Required Packages

1. Depending on your operating system version, run the respective installation command as the root user:
   • On Red Hat Enterprise Linux 6 and 5:

     # yum install krb5-workstation mod_auth_kerb elinks

   • On Red Hat Enterprise Linux 7:

     # yum install httpd22 httpd22-devel mod_auth_kerb-eap6 apr-util-ldap krb5-workstation elinks

2. When prompted, press y to proceed.
3. When the installation is complete, run the following command to check that the packages are installed:
   • On Red Hat Enterprise Linux 6 and 5:

     # rpm -q krb5-workstation mod_auth_kerb elinks

   • On Red Hat Enterprise Linux 7:

     # rpm -q httpd22 httpd22-devel mod_auth_kerb-eap6 apr-util-ldap krb5-workstation elinks

   If the packages are installed, the command output shows the package names with their version numbers.
4. Install JBoss Enterprise Web Server either from a ZIP file (Section 2.4, “Installing Enterprise Web Server from a ZIP File”) or from RPMs (Section 2.5, “Installing Enterprise Web Server from RPM Packages”).

Procedure 2.3. Installing Java

1. Subscribe your system to the appropriate channel:
   • Red Hat Enterprise Linux Server Supplementary for Red Hat Enterprise Linux 7
   • Red Hat Enterprise Linux Server Supplementary for Red Hat Enterprise Linux 6
   • Red Hat Enterprise Linux Supplementary for Red Hat Enterprise Linux 5
2. On the command line, as the root user run the command to install Java 1.6 or 1.7:
   • On Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6, and Red Hat Enterprise Linux 7, execute the yum install command to install Java 1.6:

     # yum install java-1.6.0-<VENDOR>-devel

     Substitute <VENDOR> with sun, ibm, or openjdk.
     Execute the following variation of the listed command to install Java 1.7:

     # yum install java-1.7.0-<VENDOR>-devel

     Substitute <VENDOR> with oracle, ibm, or openjdk.
3. Run the following commands as the root user (if switching from another user, make sure to run the command su -) to make sure the correct JDK is in use:

   # alternatives --config java

   # alternatives --config javac

   These commands return lists of available JDK versions with the version in use marked with a plus (+) sign. If the set JDK is not the desired option, switch to the right JDK as instructed on the command line.

   Important

   Any software that makes use of the java and javac commands is using the JDK set by alternatives. Switching java alternatives may negatively influence running of such software.
4. Install the required packages (see Section 2.3.2, “ZIP Installation Prerequisites”)

Procedure 2.4. Downloading the Enterprise Web Server ZIP File

1. Open http://access.redhat.com in your web browser.
2. In the upper right corner, click the Log in button.
3. Enter your login information and click Log in.
4. Hover over the Downloads option in the menu bar at the top of the page and under JBoss Enterprise Middleware in the displayed menu, click Downloads.
5. In the Product drop-down box column, click Web Server.
6. On the Software Downloads page, select the product version in the Version drop-down box and in the Releases tab below, click the JBoss EWS link with the correct version.
7. On the Software Details page, click the Download button next to the File drop-down box for the jboss-ews-application-servers-2.1.0-<platform>-<architecture>.zip and jboss-ews-httpd-2.1.0-<platform>-<architecture>.zip files.

   Note

   Download the appropriate versions for the target platform and architecture.
8. Confirm the file downloads have successfully completed.
9. Follow Procedure 2.5, “Extracting the ZIP File” to extract the JBoss Enterprise Web Server ZIP files.

Procedure 2.5. Extracting the ZIP File

1. On the command line, change to the directory with the ZIP files.
2. Run the following unzip command, once for each ZIP file:

   unzip <FILE_NAME> -d <TARGET_DIRECTORY> 

   Substitute FILE_NAME with the name of each downloaded file and TARGET_DIRECTORY with the path to the target directory. After the ZIP files are extracted, configure the environment before running JBoss Enterprise Web Server (see Section 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

Procedure 2.14. Running Tomcat on Red Hat Enterprise Linux

1. After extracting the zip file, check to see if a user called tomcat exists on the system by running the following command:

   id tomcat

2. If the user does not exist, use the following command to add it:

   groupadd -g 91 -r tomcat
   useradd -c "Tomcat" -u 91 -g tomcat -s /bin/sh -r tomcat

3. If the tomcat user will be running Tomcat, change the ownership of the tomcat directories.
   1. Use the following command for Tomcat 6:

      chown -R tomcat:tomcat tomcat6

      • Use the following command for Tomcat 7:

        chown -R tomcat:tomcat tomcat7

4. Test that the tomcat user has execution permission to the tomcat install path.
5. Set the JAVA_HOME variable. Use one of the following approaches to set this variable.
   1. Provide the value for JAVA_HOME externally by setting the value prior to starting Tomcat.
      • Set the value for JAVA_HOME in the setenv.sh file. In Tomcat 6, this file is available at tomcat6/bin/ and in Tomcat 7, this file is available at tomcat7/bin/. This value is loaded from catalina.sh and overrides all other set values for JAVA_HOME.

Procedure 2.15. Removing tomcatjss Package

1. At the shell prompt, become the root user.
2. Run the following uninstall command:

   # yum remove tomcatjss

Procedure 2.16. Subscribing to Red Hat Network Enterprise Channels

1. Go to Red Hat Network Enterprise.
2. Unsubscribe your system from the Red Hat Application Stack channel.
3. Subscribe to the JBoss Enterprise Web Server channels (see Section 2.5.3, “RHN Channels for JBoss Enterprise Web Server Installation Packages”).

Procedure 2.17. Subscribing to Red Hat Subscription Management Repositories

1. Go to Red Hat Subscription-Manager..
2. Click on the appropriate Units or Subscription Management Applications.
3. Subscribe to the JBoss Enterprise Web Server repositories (see Section 2.5.4, “Red Hat Subscription Management Repositories for JBoss Enterprise Web Server Installation Packages”).

Procedure 2.18. Installing Enterprise Web Server from RPM Packages

1. At the shell prompt, become the root user.
2. To install JBoss Enterprise Web Server as a group of packages, run the installation command:

   # yum groupinstall jboss-ews2

   • To install all packages in the group individually, on Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 5:

     # yum install <LIST_OF_PACKAGES>

     Substitute the <LIST_OF_PACKAGES> with names of the packages separated with spaces.
     To install all JBoss Enterprise Web Server packages, run this command:

     # yum install httpd mod_auth_kerb mod_cluster mod_cluster-native mod_jk-ap22 mod_rt mod_snmp mod_cluster-tomcat6 mod_cluster-tomcat7 tomcat6 tomcat6-admin-webapps tomcat6-webapps tomcat7 tomcat7-admin-webapps tomcat7-webapps tomcat-native

3. Verify the system is using the correct javac and java (for details see Procedure 2.3, “Installing Java”).

Procedure 2.19. Installing the JBoss Enterprise Web Server Plus Group of Packages

1. At the shell prompt, become the root user.
2. To install JBoss Enterprise Web Server Plus group of packages, run the installation command:

   # yum groupinstall jboss-ews2plus

   • To install all packages in the group individually, on Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 6, and Red Hat Enterprise Linux 5:

     # yum install <LIST_OF_PACKAGES>

     Substitute the <LIST_OF_PACKAGES> with names of the packages separated with spaces.
     To install all JBoss Enterprise Web Server Plus packages, run this command:

     # yum install hibernate-jpa-2.0-api hibernate3-commons-annotations hibernate4-eap6 hibernate4-core-eap6 hibernate4-envers-eap6 hibernate4-entitymanager-eap6 hibernate4-c3p0-eap6

Procedure 2.20. Removing SSL

1. At the shell prompt, become the root user.
2. Run the respective uninstall command:
   • on Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 6, and Red Hat Enterprise Linux 5:

     # yum remove mod_ssl

Procedure 2.21. Removing log4j From Tomcat 6

1. At the shell prompt, become the root user.
2. Run the respective uninstall command:
   • on Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 6, and Red Hat Enterprise Linux 5:

     # yum remove tomcat6-log4j

Procedure 2.22. Configuring mod_jk

1. Install the template mod_jk configuration file:

   # cp /usr/share/doc/mod_jk-ap22-*/mod_jk.conf.sample /etc/httpd/conf.d/mod_jk.conf

2. Install the template workers.properties file:

   # cp /usr/share/doc/mod_jk-ap22-*/workers.properties.sample /etc/httpd/conf/workers.properties

3. 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, see http://kbase.redhat.com/faq/docs/DOC-15836.

Procedure 2.23. Configuring mod_cluster

1. 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.
2. Configure the server to load the JBoss HTTP Connector modules:
   1. Create the file /etc/httpd/conf.d/JBoss_HTTP.conf.
   2. Add the following lines to the JBoss_HTTP.conf file:

      LoadModule slotmem_module modules/httpd/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 2.24. Running Tomcat

1. At the shell prompt, become the root user.
2. Run the following start command with the <VERSION> substituted with the correct Tomcat version (6 or 7):

   # service tomcat<VERSION> start

3. Go to http://localhost:8080 in your web browser to verify that Tomcat is running. The Apache Software Foundation page appears.

   Note

   In JBoss Enterprise Web Server installations from the RPM packages, the only supported way of running Tomcat is the running described in this section.

Procedure 2.25. Running HTTP

1. At the shell prompt, become the root user.
2. Run the following start command:
   • On Red Hat Enterprise Linux 6 or Red Hat Enterprise Linux 5:

     # service httpd start

Procedure 2.26. Stopping Tomcat

1. At the shell prompt, become the root user.
2. Run the following service command with the <VERSION> substituted with the correct Tomcat version (6 or 7):

   # service tomcat<VERSION> stop

3. Go to http://localhost:8080 in your web browser to verify that Tomcat is no longer running.

Procedure 2.27. Stopping HTTP

1. At the shell prompt, become the root user.
2. Run the following stop command:
   • On Red Hat Enterprise Linux 6 or Red Hat Enterprise Linux 5:

     # service httpd stop

Procedure 4.10. Running HTTP Server

1. Run the command line as the root user.
2. Run the following command to start the HTTP Server:

   sbin/apachectl start
   

   If you want your server to continue running automatically after a system reboot, add a call to the apachectl script to your system startup files.

   Note

   For complete documentation on how to start and stop the HTTP Server, see the files, http://localhost/manual/invoking.html and http://localhost/manual/stopping.html respectively.