Performance Monitoring Infrastructure client package

To learn how to use the PmiClient application and JMX connector to communicate to the Perf MBean in an appserver.

A Performance Monitoring Infrastructure (PMI) client package provides a PmiClient wrapper class to deliver PMI data to a client. As shown in the following figure, the PmiClient API uses the AdminClient API to communicate to the Perf MBean in an appserver.

The PmiClient communicates with the network manager first, retrieving an AdminClient instance to each appserver. When the PmiClient receives the instance, it uses it to communicate with the appserver directly for performance or level setting changes. Since level settings are persistent through PmiClient, we are only required to set it once, unless you want to change it.

Performance Monitoring Infrastructure and Java Management Extensions The PmiClient API does not work if the Java Management Extensions (JMX) infrastructure and Perf MBean are not running. If we prefer to use the AdminClient API directly to retrieve PMI data, you still have a dependency on the JMX infrastructure.

When using the PmiClient API, we have to pass the JMX connector protocol and port number to instantiate an object of the PmiClient. Once you get a PmiClient object, we can call its methods to list nodes, servers and MBeans, set the monitoring level, and retrieve PMI data.

The PmiClient API creates an instance of the AdminClient API and delegates the requests to the AdminClient API. The AdminClient API uses the JMX connector to communicate with the Perf MBean in the corresponding server and then returns the data to the PmiClient, which returns the data to the client.

---

Related concepts

Performance Monitoring Infrastructure client (WebSphere V4.0)

 

Related tasks

Run the new monitoring applications