Overview

This appendix describes how to setup and configure JMX on various applications servers in order to monitor them using Traverse.

The current Traverse-JMX implementation uses only transports that are part of the JMX Remote Management files distributed with JDK1.5 (RMI connectors).

Traverse supports the following protocols for remote monitoring:

• RMI
• Java Remote Method Protocol (JRMP)
• BEA (T3)

These connectors allows you to connect to an MBean in an MBean server from a remote location and perform operations on the server.

Note: A community-contributed command line utility to scan Java applications for JMX metrics is now included in the standard distribution in the <TRAVERSE_HOME>/utils directory. Applies to Linux only.

Monitoring an Application Server from Traverse

1. Add JMX related-configurations to the application server that you want to monitor.
2. Start the server.
3. (optional) Verify the server status and that MBeans is available through jconsole's local tab/remote tab.
4. Log in to Traverse and create a device with the IP address of the Application Server.
5. In Traverse, add a JMX Standard Test. See JMX Monitor for more information.

Note: Enter a value in the optional Domain Name field. This filters the MBeans based on the domain name you enter here. Enter comma-separated values for more than one domain names.