Installation Guide

1. Subscribe your Red Hat Enterprise Linux system to the appropriate channel:

   • OpenJDK:

     • rhel-7-server-rpms

   • Oracle:

     • rhel-7-server-thirdparty-oracle-java-rpms

   • IBM:

     • rhel-7-server-supplementary-rpms

1. Run the following commands as the root user to ensure the correct JDK is in use:

   # alternatives --config java

   Copy to Clipboard Toggle word wrap

   # alternatives --config javac

   Copy to Clipboard Toggle word wrap

   These commands return lists of available JDK versions with the selected version marked with a plus (+) sign. If the selected JDK is not the desired one, change to the desired JDK as instructed in the shell prompt.

   Important

   All software that use the java and javac commands uses the JDK set by alternatives. Changing Java alternatives may impact on the running of other software.

Removing the tomcatjss Package

1. As the root user, run the following command to remove tomcatjss:

   # yum remove tomcatjss

   Copy to Clipboard Toggle word wrap

Downloading JBoss Web Server

1. Open a browser and log in to the Red Hat Customer Portal.
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.1 Application Server (jws-application-servers-3.1.0-<platform>-<architecture>.zip)

Extracting JBoss Web Server

1. Unzip the downloaded ZIP files to your installation directory.

   The directory created by extracting the ZIP archives is the top-level directory for JBoss Web Server. This is referred to as JWS_HOME.

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 53 -r tomcat

   Copy to Clipboard Toggle word wrap

3. Run the following command to create the tomcat user in the tomcat user group:

   # useradd -c "Tomcat" -u 53 -g tomcat -s /bin/sh -r tomcat

   Copy to Clipboard Toggle word wrap

4. Check that the tomcat user group and the tomcat user were created correctly:

   $ grep tomcat /etc/group
   
   tomcat:x:53
   
   $ grep tomcat /etc/passwd
   
   tomcat:x:53:53:Tomcat:/home/tomcat:/bin/sh

   Copy to Clipboard Toggle word wrap

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

   Copy to Clipboard Toggle word wrap

   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.

6. Ensure that the tomcat user has execute permissions to all parent directories. For example:

   # chmod -R u+X tomcat<VERSION>

   Copy to Clipboard Toggle word wrap

1. Change directory to JWS_HOME/extras/:

   # cd JWS_HOME/extras/

   Copy to Clipboard Toggle word wrap

2. Copy log4j-eap6.jar and log4j.properties from JWS_HOME/extras/ to JWS_HOME/lib.

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

   Copy to Clipboard Toggle word wrap

   Replace <VERSION> with the Tomcat version number (7 or 8).

3. Change directory to JWS_HOME/tomcat<VERSION>/extras/:

   # cd ../tomcat<VERSION>/extras/

   Copy to Clipboard Toggle word wrap

4. Copy tomcat-juli-adapters.jar from JWS_HOME/tomcat<VERSION>/extras to JWS_HOME/tomcat<VERSION>/lib.

   # cp tomcat-juli-adapters.jar ../lib/

   Copy to Clipboard Toggle word wrap

5. Replace JWS_HOME/tomcat<VERSION>/bin/tomcat-juli.jar with JWS_HOME/tomcat<VERSION>/extras/tomcat-juli.jar:

   # cp tomcat-juli.jar ../bin/

   Copy to Clipboard Toggle word wrap

Starting Tomcat

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

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

   Copy to Clipboard Toggle word wrap
   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 the Jsvc chapter.

Stopping Tomcat

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

   Copy to Clipboard Toggle word wrap

1. Log in to the Red Hat Subscription Manager.
2. Click on the Systems tab.
3. Click on the Name of the system to add the subscription to.
4. Change from the Details tab to the Subscriptions tab, then click Attach Subscriptions.
5. Select the check box beside the subscription to attach, then click Attach Subscriptions.

Installing JBoss Web Server from RPM packages using YUM

1. On a command line, subscribe to the JBoss Web Server CDN repositories for your operating system version using subscription-manager:

   # subscription-manager repos --enable <repository>

   Copy to Clipboard Toggle word wrap

   • For Red Hat Enterprise Linux 7:

     • jws-3-for-rhel-7-server-rpms
     • jb-coreservices-1-for-rhel-7-server-rpms

1. Issue the following command as the root user to install JBoss Web Server:

   # yum groupinstall jws3

   Copy to Clipboard Toggle word wrap
   Note
   • Although not recommended, instead of using the group install, you can install each of the packages and their dependencies individually.
   • The Red Hat JBoss Core Services repositories above are required for the installation of JBoss Web Server.

Starting Tomcat

1. In a shell prompt as the root user, start the Tomcat service. Replace <VERSION> with the desired Tomcat version (7 or 8):

   1. For Red Hat Enterprise Linux 7:

      # systemctl start tomcat<VERSION>.service

      Copy to Clipboard Toggle word wrap

1. To verify that Tomcat is running, the output of the service status command should be reviewed. This can be executed as any user.

   1. For Red Hat Enterprise Linux 7:

      # systemctl status tomcat<VERSION>.service

      Copy to Clipboard Toggle word wrap

Stopping Tomcat

1. In a shell prompt as the root user, stop the Tomcat service. Replace <VERSION> with the desired Tomcat version (7 or 8):

   1. For Red Hat Enterprise Linux 7:

      # systemctl stop tomcat<VERSION>.service

      Copy to Clipboard Toggle word wrap

2. To verify that Tomcat is no longer running, the output of the service status command should be reviewed. This can be executed as any user.

   1. For Red Hat Enterprise Linux 7:

      # systemctl status tomcat<VERSION>.service

      Copy to Clipboard Toggle word wrap

1. Install the selinux-policy-devel package:

   yum install -y selinux-policy-devel

   Copy to Clipboard Toggle word wrap

2. Execute the .postinstall.selinux script:

   cd <JWS_home>/tomcat<version>
   sh .postinstall.selinux

   Copy to Clipboard Toggle word wrap

   Where tomcat<version> refers to tomcat7 or tomcat8.

3. Make and install the SELinux module:

   cd selinux
   make -f /usr/share/selinux/devel/Makefile
   semodule -i tomcat<version>.pp

   Copy to Clipboard Toggle word wrap

4. Apply the SELinux contexts for JBoss Web Server:

   restorecon -r <JWS_home>/tomcat<version>/

   Copy to Clipboard Toggle word wrap

5. Add access permissions to the required ports for JBoss Web Server:

   semanage port -a -t http_port_t -p tcp 8005
   semanage port -a -t http_port_t -p tcp 8080
   semanage port -a -t http_port_t -p tcp 8009
   semanage port -a -t http_port_t -p tcp 8443

   Copy to Clipboard Toggle word wrap

6. Start the Tomcat service:

   <JWS_home>/bin/startup.sh

   Copy to Clipboard Toggle word wrap

7. Check the context of the running process expecting tomcat_<version>__t:

   ps -eZ | grep tomcat | head -n1

   Copy to Clipboard Toggle word wrap

8. To verify the contexts of the Tomcat directories, for example:

   ls -lZ <JWS_home>/tomcat<version>/logs/

   Copy to Clipboard Toggle word wrap

1. In a shell prompt become the root user.

2. Configure the JMX JAVA_OPTS properties in the /usr/sbin/tomcat<VERSION> file in the start and start-security sections.

   if [ "$1" = "start" ]; then
   JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.port=8100 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=true -Dcom.sun.management.jmxr
   emote.access.file="/etc/tomcat<VERSION>/jmxremote.access" -Dcom.sun.management.jmxremote.password.file="/etc/tomcat<VERSION>/jmxremote.password""
   
     ${JAVACMD} $JAVA_OPTS $LOGGING_CONFIG $CATALINA_OPTS \
       -classpath "$CLASSPATH" \
       -Dcatalina.base="$CATALINA_BASE" \
       -Dcatalina.home="$CATALINA_HOME" \
       -Djava.endorsed.dirs="$JAVA_ENDORSED_DIRS" \
       -Djava.io.tmpdir="$CATALINA_TMPDIR" \
       org.apache.catalina.startup.Bootstrap start \
        >> ${CATALINA_BASE}/logs/catalina.out 2>&1 &
       if [ ! -z "$CATALINA_PID" ]; then
         echo $! > $CATALINA_PID
       fi
   elif [ "$1" = "start-security" ]; then
   JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.port=8100 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=true -Dcom.sun.management.jmxr
   emote.access.file="/etc/tomcat<VERSION>/jmxremote.access" -Dcom.sun.management.jmxremote.password.file="/etc/tomcat<VERSION>/jmxremote.password""
   
     ${JAVACMD} $JAVA_OPTS $LOGGING_CONFIG $CATALINA_OPTS \
       -classpath "$CLASSPATH" \
       -Dcatalina.base="$CATALINA_BASE" \

   Copy to Clipboard Toggle word wrap

3. Run the following command to start Tomcat:

   service tomcat<VERSION> start

   Copy to Clipboard Toggle word wrap
4. Start the JBoss ON agent.
5. In the JBoss ON Web UI, import the JBoss ON agent and Tomcat.
6. In the JBoss ON Web UI, setup the Tomcat connection configuration (principal and credentials).

7. In the JBoss ON Web UI, set the Tomcat Control method configuration to RPM System V init script.

   Note

   The Start and Shutdown script may not be set because the Tomcat plugin always runs the service tomcat<VERSION> start/stop command for the RPM System V init script configuration setting.

1. Create the jmxremote.access file with controlRole readwrite in the C:\jmx directory.

2. Create the jmxremote.password file with controlRole pwd in the C:\jmx directory.

   Note

   Set the owner of jmxremote.access and jmxremote.password to SYSTEM, and restrict the access of jmxremote.password only to SYSTEM. The SYSTEM user must only have read access.

3. Enable JMX for the Tomcat Windows service:

   JWS_HOME\sbin\tomcat<VERSION>.exe //US//Tomcat<VERSION> ++JvmOptions="-Dcom.sun.management.jmxremote.port=8100;-Dcom.sun.management.jmxremote.access.file="C:\jmx\jmxremote.access";-Dcom.sun.management.jmxremote.password.file="C:\jmx\jmxremote.password";-Dcom.sun.management.jmxremote.ssl=false;-Dcom.sun.management.jmxremote.authenticate=true"

   Copy to Clipboard Toggle word wrap
4. Start the Tomcat Windows service, and verify that it is running.
5. Install and configure the JBoss ON agent. Type discovery in the agent prompt to discover the Tomcat Windows service.
6. In the JBoss ON Web UI, click Inventory, then click Discovery Queue, and select import Tomcat and RHQ agent.
7. In the JBoss ON Web UI, go to Platforms and search for the agent name. Click on your agent.
8. On the Agent page, Tomcat Servers are listed. Select your Tomcat server by clicking it.
9. In the JBoss ON Web UI, click on the Inventory tab and then configure the Tomcat Server in Connection Settings.
10. Enter the Principal and Credentials information. Use the controlRole and password set in the jmxremote files.

11. Set the control method to RPM System V init script.

    Note

    You cannot set Start and Shutdown script fields.

12. Click Save.
13. Update the connection settings of the Tomcat Server JVM, and set Principal and Credentials.