Foglight for JMX 5.9.8 - User Guide

Generic JDK5+ Platform MBean Server

Some application servers, such as Apache Tomcat, do not provide their own MBean server remote access method. In such cases, you can enable a standard JDK remote JMX access mechanism by adding -D parameters to the Java command-line in the application server's startup scripts.

For a full description of the available options, see:
http://download.oracle.com/javase/1.5.0/docs/guide/management/agent.html

For a simple description for Apache Tomcat, see Enabling JMX Remote:
http://tomcat.apache.org/tomcat-6.0-doc/monitoring.html

The following code block is an example of the required parameters:

-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=<JMXPORT>
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false

where <JMXPORT> is an available port number that the MBean server can listen on for connections from the JMX agent.

IBM WebSphere 7

WebSphere does not use the Platform MBean Server to host its own MBeans, so the JMX agent is not able to collect JVM data through its normal connection. Unlike JBoss and WebLogic, it is not possible to configure WebSphere to use the Platform MBean Server in this way.

The JMX agent provides an alternative mechanism for gathering JVM data for this situation. It collects JVM data from a secondary port by enabling generic remote access to the platform MBean server.

Add the following parameters to the Generic JVM Arguments for the application server:

-Djavax.management.builder.initial=
-Dcom.sun.management.jmxremote

IMPORTANT: The first parameter ends in an equals sign (=); the second parameter does not.

If your WebSphere environment includes more than one application server using the same JVM and you do not want to affect all processes started from that JVM, add the following lines to the Generic JVM Arguments as well:

-Dcom.sun.management.jmxremote.port=<JMXPORT>
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false

Alternatively, you can add the following lines to java/jre/lib/management/management.properties file in the WAS_HOME directory, outside of the profiles directory:

com.sun.management.jmxremote.port=<JMXPORT>
com.sun.management.jmxremote.authenticate=false
com.sun.management.jmxremote.ssl=false

NOTE: You must restart the application server in order for these settings to take effect.

When configuring the Service URL for WebSphere using the Connection Info Assistant (see Step 5 of the procedure in Creating JMX Agents Using the Connection URL), set the BOOTRSTRAP_PORT to the port number from the BOOTSTRAP_ADDRESS in the WebSphere administration console Ports page, and set the JVM_DATA_PORT to <JMXPORT>. These port numbers must be different.

JBoss 5

JBoss does not use the Platform MBean Server to host its own MBeans. Therefore the JMX agent cannot collect JVM data unless you add the following parameter to the JBoss Java command-line:

-Djboss.platform.mbeanserver

This parameter forces JBoss to use the Platform MBean Server.

JBoss EAP 4.3, 5

The JBoss Enterprise Application Platform (EAP) does not provide its own MBean server remote access method. You can enable a standard JDK remote JMX access mechanism by adding -D parameters to the Java command-line in the application server's startup scripts.

For a full description of the available options, see:
http://download.oracle.com/javase/1.5.0/docs/guide/management/agent.html

The following code block is an example of the required parameters:

-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=<JMXPORT>
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false

where <JMXPORT> is an available port number that the MBean server can listen on for connections from the JMX agent.

You must also add the following parameters:

-Djboss.platform.mbeanserver ‑Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl

NOTE: Due to the formatting of this document, the parameter may appear as two lines. It must be entered as a single line in the startup script.