Installation Guide

Procedure 3.1. Installing Java Development Kit (JDK) for Microsoft Windows

1. Download the Oracle JDK 1.7 or 1.8 for your operating system and architecture. You can download the JDK installation file from the Oracle website: http://www.oracle.com/technetwork/java/javase/downloads/index.html.
2. Double-click the downloaded file to start the Java installation.
3. Proceed as instructed in the installation window.

Procedure 3.2. 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 3.3. Extract JBoss Web Server

• Unzip the downloaded ZIP files to your installation directory.

  Note

  We recommend that you install JBoss Web Server in C:\Program Files.

Procedure 3.4. Setting Environment Variables

1. Log in to an account with local administrator permissions.
2. Go to Control Panel → System.
3. Click on the Advanced tab.
4. Click the Environment Variables button.
5. Click the New for System Variables.
6. For JAVA_HOME, TMP and TEMP, enter the appropriate name-value pairs for your system.
7. For the SSL Connector to work, you will also need to add JWS_HOME\bin to the PATH environment variable of the user that the services will run under. This is SYSTEM by default.

Procedure 3.5. Running the Post-Installation Scripts

1. Open a Command Prompt with administrator privileges.
2. Change to the etc folder of your JBoss Web Server installation:

   cd /D "JWS_HOME\etc"

   Copy to Clipboard Toggle word wrap
3. Run the Apache HTTP Server and Tomcat post-installation scripts with the following commands:

   call postinstall.httpd.bat

   Copy to Clipboard Toggle word wrap

   call postinstall.tomcat.bat

   Copy to Clipboard Toggle word wrap
   The scripts create the required symbolic links (Junction Points) for temporary logging and configuration directories.

Procedure 3.6. Installing the Tomcat Service

1. Open a Command Prompt with administrator privileges.
2. Change to the bin folder for your Tomcat version:

   cd /D "JWS_HOME\share\tomcat<VERSION>\bin"

   Copy to Clipboard Toggle word wrap
3. Install the Tomcat service with the following command:

   call service.bat install

   Copy to Clipboard Toggle word wrap

Procedure 3.7. Installing the Apache HTTP Server Service

1. Open a Command Prompt with administrator privileges.
2. Change to the bin folder of your JBoss Web Server installation:

   cd /D "JWS_HOME\bin"

   Copy to Clipboard Toggle word wrap
3. Install the Apache HTTP Server service with the following command:

   httpd -k install

   Copy to Clipboard Toggle word wrap
   A Firewall security dialog prompt may appear asking for networking access for the Apache HTTP Server. Click Allow to access this service from the network.

Procedure 3.8. Enabling log4j Logging for Tomcat

1. Open a Command Prompt with administrator privileges.
2. Change to JWS_HOME\share\extras\
3. Copy the log4j files to the lib folder for your Tomcat version:

   copy log4j-eap6.jar log4j.properties tomcat-juli-adapters.jar ..\tomcat<VERSION>\lib

   Copy to Clipboard Toggle word wrap
4. Replace tomcat-juli.jar file in your Tomcat bin directory with the tomcat-juli.jar file from JWS_HOME\share\extras\:

   copy tomcat-juli.jar ..\tomcat<VERSION>\bin

   Copy to Clipboard Toggle word wrap

Procedure 3.9. Removing/Re-Adding SSL Support

1. Open a file browser and go to JWS_HOME\etc\httpd\conf.d.
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 mod_jk

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

Procedure 3.11. Configuring mod_cluster

1. In JWS_HOME\etc\httpd\conf.modules.d\00-proxy.conf, ensure that there is a # at the beginning of the following line to disable mod_proxy_balancer.so:

   LoadModule proxy_balancer_module modules/mod_proxy_balancer.so

   Copy to Clipboard Toggle word wrap
   This module is incompatible with mod_cluster.
2. Configure the server to load the mod_cluster modules:
   1. Create the file JWS_HOME\etc\httpd\conf.d\mod_cluster.conf.
   2. Add the following lines to mod_cluster.conf:

      LoadModule proxy_cluster_module modules/mod_proxy_cluster.so
      LoadModule cluster_slotmem_module modules/mod_cluster_slotmem.so
      LoadModule manager_module modules/mod_manager.so
      LoadModule advertise_module modules/mod_advertise.so

      Copy to Clipboard Toggle word wrap

Procedure 3.12. Configuring Folder Permissions for JBoss Web Server Services

1. Right-click the JWS_HOME folder and click Properties.
2. Select the Security tab.
3. Click the Edit button.
4. Click the Add button.
5. In the text box, enter LOCAL SERVICE.
6. Select the Full Control check box for the LOCAL SERVICE account.
7. Click OK.
8. Click the Advanced button.
9. Inside the Advanced Security Settings dialog, select LOCAL SERVICE and click Edit.
10. Select the check box next to the Replace all existing inheritable permissions on all descendants with inheritable permissions from this object option.
11. Click OK through all the open folder property windows to apply the settings.

Procedure 3.13. Starting JBoss Web Server from the Command Prompt

1. Open a Command Prompt with administrator privileges.
2. Start the Tomcat service:

   net start tomcat<VERSION>

   Copy to Clipboard Toggle word wrap
3. Start the Apache HTTP Server (httpd) service:

   net start Apache2.4

   Copy to Clipboard Toggle word wrap

Procedure 3.14. Starting JBoss Web Server from the Computer Management Tool

1. Go to Start → Administrative Tools → Services
2. In the Services list, right-click the name of each service (httpd and tomcat) and click Start.

Procedure 3.15. Stopping JBoss Web Server from the Command Prompt

1. Open a Command Prompt with administrator privileges.
2. Stop the Tomcat service:

   net stop tomcat<VERSION>

   Copy to Clipboard Toggle word wrap
3. Stop the Apache HTTP Server (httpd) service:

   net stop Apache2.4

   Copy to Clipboard Toggle word wrap

Procedure 3.16. Stopping JBoss Web Server from the Computer Management Tool

1. Go to Start → Administrative Tools → Services
2. In the Services list, right-click the name of each service (httpd and tomcat) and click Stop.

Procedure 4.1. Installing Java

1. Download the Oracle JDK 1.7 or 1.8 for your operating system and architecture. You can download the JDK installation file from the Oracle website: http://www.oracle.com/technetwork/java/javase/downloads/index.html.
2. Run the Java installation file.
3. Open /usr at a shell prompt, and run the following command to display the current Java symbolic link:

   ls -lad java

   Copy to Clipboard Toggle word wrap
4. Remove the link:

   rm java

   Copy to Clipboard Toggle word wrap
5. Create a Java symbolic link to the newly installed JDK:

   ln -sf /usr/jdk/<JDK>

   Copy to Clipboard Toggle word wrap

Procedure 4.2. 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 4.3. 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 4.4. Running the Post-Installation Scripts

1. Open a shell prompt, and change directory to JWS_HOME/etc.
2. Issue the following commands to run the post-installation scripts:

   sh .postinstall.httpd
   sh .postinstall.tomcat
   

   Copy to Clipboard Toggle word wrap
   The post-installation scripts create the Apache and Tomcat users and groups.

Procedure 4.5. Setting the JAVA_HOME Environment Variable

1. Open the Tomcat configuration file:
   • For Tomcat 7: JWS_HOME/etc/sysconfig/tomcat7
   • For Tomcat 8: JWS_HOME/etc/sysconfig/tomcat8
2. Remove the hash (#) sign at the beginning of the following line:

   # JAVA_HOME="/usr/java"

   Copy to Clipboard Toggle word wrap

Procedure 4.6. Removing/Re-Adding SSL Support

• Go to JWS_HOME/etc/httpd/conf.d and rename the SSL configuration file:
  • To remove SSL, rename ssl.conf to ssl.conf.disabled.
  • To re-add the SSL, rename ssl.conf.disabled to ssl.conf.

Procedure 4.7. Enabling log4j Logging for Tomcat

1. Open a shell prompt and change directory to JWS_HOME/share/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:

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

   Copy to Clipboard Toggle word wrap

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

   Copy to Clipboard Toggle word wrap

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

   Copy to Clipboard Toggle word wrap
   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/share/extras/:

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

   Copy to Clipboard Toggle word wrap

Procedure 4.8. Configuring mod_jk

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

Procedure 4.9. Configuring Apache HTTP Server to Use 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 4.10. Starting Tomcat

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

  $ sh JWS_HOME/share/apache-tomcat-<VERSION>/bin/daemon.sh

  Copy to Clipboard Toggle word wrap

  Important

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

Procedure 4.11. Starting Apache HTTP Server

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

  # ./apachectl start

  Copy to Clipboard Toggle word wrap

Procedure 4.12. Stopping Tomcat

• To stop Tomcat, in a shell prompt as the root user change to JWS_HOME/sbin/ and run the following command with your respective Tomcat version (7 or 8):

  tomcat<VERSION> stop

  Copy to Clipboard Toggle word wrap

Procedure 4.13. Stopping Apache HTTP Server

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

  apachectl stop

  Copy to Clipboard Toggle word wrap

Procedure 5.1. Start Tomcat Using Jsvc on Red Hat Enterprise Linux

• Run the following command to start Tomcat using Jsvc on Red Hat Enterprise Linux:

  JWS_HOME/tomcat<VERSION>/bin/daemon.sh start

  Copy to Clipboard Toggle word wrap

Procedure 5.2. Start Tomcat Using Jsvc on Solaris

• Run the following command to start Tomcat using Jsvc on Solaris:

  JWS_HOME/share/tomcat<VERSION>/bin/daemon.sh start

  Copy to Clipboard Toggle word wrap

Procedure 5.3. Stop Tomcat Using Jsvc on Red Hat Enterprise Linux

• Run the following command to stop Tomcat that was started using Jsvc on Red Hat Enterprise Linux:

  JWS_HOME/tomcat<VERSION>/bin/daemon.sh stop

  Copy to Clipboard Toggle word wrap

Procedure 5.4. Stop Tomcat Using Jsvc on Solaris

• Run the following command to stop Tomcat that was started using Jsvc on Solaris:

  JWS_HOME/share/tomcat<VERSION>/bin/daemon.sh stop

  Copy to Clipboard Toggle word wrap

Procedure 7.1. Download the Web Server Plugin Pack for JBoss ON

1. Open a web browser, and log in to the Red Hat Customer Portal: http://access.redhat.com
2. Click Downloads.
3. Click Red Hat JBoss Web Server in the Product Downloads list.
4. Select JBoss ON for Web Server in the Product drop-down menu.
5. Click Download for each of the following files:

   • Web Server Plugin Pack for Red Hat JBoss Operations Network

Procedure 7.2. Configuring Apache HTTP Server for JBoss ON Monitoring

1. As the apache user, enable the mod_bmx modules. Create the file JWS_HOME/httpd/conf.d/mod_bmx.conf with the following contents:

   LoadModule bmx_module modules/mod_bmx.so
   LoadModule bmx_status_module modules/mod_bmx_status.so
   LoadModule bmx_vhost_module modules/mod_bmx_vhost.so

   Copy to Clipboard Toggle word wrap
2. Add a handler for mod_bmx. In JWS_HOME/httpd/conf/httpd.conf, append your handler definition. For example:

   <Location /bmx>
   SetHandler bmx-handler
   </Location>
   

   Copy to Clipboard Toggle word wrap
   You may want to restrict access to this URL to a specific virtual host or use password authentication.
3. Restart the Apache HTTP Server. You can access http://SERVER_ADDRESS:PORT/bmx in a web browser to verify that mod_bmx is working correctly.
4. The Apache HTTP Server in your JBoss Web Server installation will now be discoverable for JBoss ON. In JBoss ON, you can import it from the Discovery Queue.
   Consult the JBoss ON documentation for further details on monitoring and managing Apache HTTP Server.

Procedure 7.3. Configuring User Permissions on a Linux Operating System

• As a user with root privileges, run the following command to add the user which runs the JBoss ON Agent to the tomcat and apache user groups:

  # usermod -aG tomcat,apache <JBOSSON_AGENT_USER>

  Copy to Clipboard Toggle word wrap

Procedure 7.4. Configuring Tomcat for JBoss ON Monitoring

1. Open the startup file of the respective JBoss Web Server instance for editing:
   • On Red Hat Enterprise Linux installed from a ZIP file, open JWS_HOME/tomcat<VERSION>/bin/startup.sh
   • On Red Hat Enterprise Linux installed from RPM, open /usr/sbin/tomcat<VERSION>
   • On Microsoft Windows open JWS_HOME\share\tomcat<VERSION>\bin\startup.bat.
   • On Solaris using daemon.sh to start Tomcat, open JWS_HOME/tomcat<VERSION>/bin/setenv.sh
2. Define an available port for JMX monitoring. Ensure the port is not blocked by any firewall.
   • On Red Hat Enterprise Linux and Solaris:

     JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.port=PORT_NUMBER -Djava.rmi.server.hostname=IP_ADDRESS"

     Copy to Clipboard Toggle word wrap
   • On Microsoft Windows:

     set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.port=PORT_NUMBER -Djava.rmi.server.hostname=IP_ADDRESS"

     Copy to Clipboard Toggle word wrap
3. In production environments, add the following lines to the JAVA_OPTS variable in the startup file to secure JMX with SSL and restrict the access with a firewall:
   • On Red Hat Enterprise Linux and Solaris

     JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.access.file=JWS_HOME/jmxremote.access"
     JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.password.file=JWS_HOME/jmxremote.password"

     Copy to Clipboard Toggle word wrap
   • On Microsoft Windows:

     set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.access.file=JWS_HOME\jmxremote.access"
     set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.password.file=JWS_HOME\jmxremote.password"

     Copy to Clipboard Toggle word wrap

   Note

   If you want to disable authentication and SSL for development purposes, add the following lines to the JAVA_OPTS variable in the startup file:

   JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.ssl=false"
   JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.authenticate=false"

   Copy to Clipboard Toggle word wrap
4. Once the Tomcat server resource is discovered and imported into the JBoss ON inventory, it may be necessary to update the new resource's connection settings.
   1. In the JBoss ON interface, click Connection Settings for the newly imported Tomcat server resource.
   2. Verify the value of the Manager URL property to the RMI URL, to ensure it uses the correct JMX host name and port number as defined in the Tomcat server startup file. An example for this value is shown below:

      service:jmx:rmi:///jndi/rmi://$IP_ADDRESS:$PORT/jmxrmi

      Copy to Clipboard Toggle word wrap