Use PMI client to develop your monitoring application
(deprecated)
Overview
The following is the programming model for Performance Monitoring
Infrastructure (PMI) client:
Procedure
- Create an instance of PmiClient. This is used for all
subsequent method calls.
- Optional: We can create your own MBeans. Refer
to Extending the WAS administrative system with
custom MBeans.
- Call the listNodes() and listServers(nodeName) methods to find
all the nodes and servers in the WAS domain.
The PMI client provides
two sets of methods: one set in V5.0 and the other set inherited from
V4.0. We can only use one set of methods. Do not mix them together.
- Call listMBeans and listStatMembers to get all the available MBeans
and MBeanStatDescriptors.
- Call the getStats method to get the Stats object for the PMI data.
- Optional: The client can also call setStatLevel or
getStatLevel to set and get the monitoring level. Use the MBeanLevelSpec objects
to set monitoring levels.
What to do next
If you prefer
to use the V4.0 interface, the model is essentially the same, but the
object types are different:
- Create an instance of PmiClient.
- Call the listNodes() and listServers(nodeName) methods to find all the
nodes and servers in the WAS domain.
- Call listMembers to get all the perfDescriptor objects.
- Use the PMI client's get or gets method to get CpdCollection objects.
These contain snapshots of performance data from the server. The same structure
is maintained and its update method is used to refresh the data.
- (Optional) The client can also call setInstrumentationLevel or getInstrumentationLevel
to set and get the monitoring level.
See also
Performance Monitoring Infrastructure client (V4.0)
Using V5.0 PMI API in V3.5.5+ and V4.0.x
Example: Performance Monitoring Infrastructure client (Version
4.0)
Example: Performance Monitoring Infrastructure client with new data
structure
See Also
Performance Monitoring Infrastructure client package
PMI client interface (deprecated)
|