IBM Performance Management

Configuring the JBoss agent

The JBoss agent monitors the resources of JBoss application servers and the JBoss Enterprise Application platform. Use the dashboards that are provided with the JBoss agent to identify the slowest applications, slowest requests, thread pool bottlenecks, JVM heap memory and garbage collection issues, busiest sessions, and other bottlenecks on the JBoss application server. This agent is a multiple instance agent; you must create the instance first and then start the agent manually.

Before you begin

Before you use the JBoss agent to monitor the JBoss Application Server 5.1 and 6.0, you must enable the Java™ Management Extensions (JMX) service on the server. You must also add the following parameter to the JBOSS_HOME/bin/run.sh script:

"JAVA_OPTS="-Djboss.platform.mbeanserver $JAVA_OPTS"".

About this task

The Managed System Name includes the instance name that you specify, for example, instance_name:host_name:pc, where pc is your two character product code. The Managed System Name is limited to 32 characters.
The instance name that you specify is limited to 28 characters minus the length of your host name. For example, if you specify JBoss as your instance name, your managed system name is JBoss:hostname:JE.
Important: If you specify a long instance name, the Managed System name is truncated and the agent code does not display correctly.

You can run the configuration script to create an instance and change any configuration settings. You can edit the agent silent response file before you run the script to bypass the prompts and responses that are required.

Procedure