Chapter 6. Monitoring Enterprise Web Server with JBoss Operations Network

Procedure 6.1. Configuring User Permissions on a Unix Operating System

1. At the shell prompt, become the root user.
2. Run the following command to add the user, under which JON Agent runs to the tomcat and apache user groups:

   # usermod -aG tomcat,apache <RHQ_AGENT_USER>

Procedure 6.2. Configuring Monitoring

1. Open the startup file of the respective JBoss Enterprise Web Server instance for editing:
   • on Red Hat Enterprise Linux installed from a ZIP file open /opt/jboss-ews-2.0/tomcat<VERSION>/bin/startup.sh
   • on Red Hat Enterprise Linux installed from a RPM files open /usr/sbin/tomcat<VERSION>
   • on Solaris open /opt/jboss-ews-2.0/tomcat<VERSION>/bin/startup.sh
   • on Windows open $TOMCAT_HOME\bin\catalina.bat. Adjust the value of $TOMCAT_HOME based on the version of Tomcat being set up.
2. Define an available port for JMX monitoring. Make sure it is not blocked by any firewall. To do so, to the JAVA_OPTS variable in the startup file, add the following line and substitute PORT_NUMBER with the number of the port dedicated to monitoring:
   • on Red Hat Enterprise Linux and Solaris:

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

   • on Windows:

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

3. Direct the JBoss Operations Network agent to locate the JMX port defined.
   1. Click Connection Settings in the JBoss Operations Network interface.
   2. Set the value of the Manager URL property to the RMI URL at which Tomcat is available. An example for this value is as follows:

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

   3. Save the new value. The Tomcat resource now appears as fully available for JBoss Operations Network.
4. 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"
   

   Important

   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=/opt/jboss-ews-2.0/jmxremote.access"
   JAVA_OPTS="${JAVA_OPTS} -Dcom.sun.management.jmxremote.password.file=/opt/jboss-ews-2.0/jmxremote.password"
   

   on Windows:

   set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.access.file=C:\Program Files\jboss-ews-2.0\jmxremote.access"
   set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.password.file=C:\Program Files\jboss-ews-2.0\jmxremote.password"