Connecting to a JMX Data Source

Establish a connection to a Java application server to monitor MBean attributes.

  1. On the Real-Time Monitoring tab, in the Monitor group, click System.
  2. Click Select from predefined Data Sources and then click Next.
  3. Perform one of the following steps:
    • To explore all available MBean attributes on an application server, expand the Application Server folder and select a JMX recording profile from a vendor-specific folder. Profile names end with the extension .jmx.
    • To explore a selection of MBeans that contain typical attributes for monitoring, expand the Application Server folder and select a JMX recording profile from a vendor-specific folder. Profile names end with the extension .ejmx.
    • To create a generic JMX monitoring data source, expand the Custom Data folder and select JMX Data.
  4. In the Hostname text box, specify the JMX server.
  5. Optional: In the Alias text box, specify the alias name. The alias must be a highly descriptive synonym for the monitored server. It is recommended that you group measures on a particular machine. For example, both WebLogic and IIS might be installed on the same computer. Both servers require monitoring, but the two performance measures must appear in separate menu trees.
  6. Specify the port, username, and password that are appropriate for the username.
  7. If you opted to create a generic JMX monitoring data source, select a supported application configuration from the Application list box.
  8. Click Server Configuration. The JMX Connection Configuration dialog box opens.
  9. Specify the application server installation directory where the application server's communication libraries are located. The relative classpath entries of the application configuration file, together with the specified application server install directory, form the classpath under which the JMX client runs. The resulting classpath is viewed in the Resulting classpath text box.
    Note: It is recommended that you use a UNC path or copy the application library directory of the server to your local machine and specify your local copy as the application server installation directory. To complete this task, click [...] next to the App. server install directory text box.
    Note: JMX monitoring of WebSphere requires that you specify an IBM JDK. If your WebSphere server has disabled administrative security or enabled administrative security and the inbound CSIv2 transport layer is TCP/IP, you can specify a SUN JDK.
  10. In the Java home directory text box, specify the installation directory where the client's communication libraries are located. Alternative: Click [...] to navigate to the appropriate directory.
  11. Specify additional libraries in the Additional classpath text box.
  12. Specify additional virtual machine parameters in the Additional JVM parameters text box. The parameters on the Connection and Visualization pages are preconfigured for each server.
  13. Click OK. The Connection Parameters page opens.
  14. Click Next and then click Finish. Performance Explorer connects to the JMX server.
  15. Examine the exposed beans in the JMX Data Source Browser.
  16. Click Finish.