Foglight for JMX 5.9.8 - User Guide

Oracle Application Server (OAS) 10.1.3

Enable the "Enable J2SE 5.0 Platform MBeans" option as described in the following document: http://download.oracle.com/docs/cd/B31017_01/web.1013/b28950/topology.htm#BIHBDIGD.

After you enable the option, restart the relevant OC4J instances.

If the JMX agent is not deployed to an Agent Manager running on the same host as the Oracle Application Server, the agent requires a local copy of the JAR files from the Oracle Application Server.

NOTE: The directory structure below the Oracle Application Server installation directory ($ORACLE_HOME) must be preserved in the copy created on the agent host.

The following directories contain the required JAR files:

Oracle WebLogic 10

WebLogic typically uses and only provides remote access to its own MBean Server, which is separate from the Platform MBean Server. As a result, when the JMX agent connects to the WebLogic MBean Server, it is unable to collect JVM data.

Oracle WebLogic 10 provides an option called "Platform MBean Server Enabled" in the Advanced section of the Domain General configuration page. This option must be enabled to force WebLogic to use the Platform MBean Server instead of a separate MBean Server. Enabling this option allows the JMX agent to collect both WebLogic MBean data and JVM data.

NOTE: This option is enabled by default in WebLogic 10.3.3 and later.

WebLogic version 10.3.3 and later have an additional option called Platform MBean Server Used that must also be enabled in order for the JMX agent to collect JVM data.

Resin 4

Resin 4 provides a command-line option to enable remote JMX access:
-jmx-port <JMXPORT>

where <JMXPORT> is an available port number that the MBean Server can listen on for connections from the JMX agent. This is essentially a shortcut for the standard JDK remote access mechanism described in Generic JDK5+ Platform MBean Server .

Installing Foglight for JMX

The Java Management Extensions (JMX) API is a standard application programming interface (API) for management and monitoring of resources such as applications, devices, services, and Java virtual machines (JVMs). Foglight for JMX uses this technology to collect and display JMX metrics from local and remote MBean servers.

Foglight for JMX is designed to help system developers and production specialists diagnose and solve performance issues in pre-production and production Java environments.

You can create and configure JMX agents for monitoring your application servers through the Application Servers Administration dashboard. Typically, you create a JMX agent instance for each application server that you want to monitor. These agents are responsible for collecting performance and monitoring data from the JMX-enabled application servers. The Application Servers > Monitor dashboard displays the collected data, and the status of the MBean server and JVM. Use the JMX > Explorer dashboard to view the MBean Object Name, metrics, properties, and relationship.

NOTE: The Application Servers Administration dashboard is available to users with the “JMX Administrator” role only. The JMX Explorer dashboard is available to users with the “JMX Administrator”, or the “JMX Read-only User” roles. For more information on groups, roles, and users, refer to the Foglight Administration and Configuration Guide.