Operating Systems: i5/OS
             Personalize the table of contents and search results
PMI data collection
PMI data collection can occur in three different interfaces, Java
Management Extension (JMX) interface (J2EE MBeans and WebSphere Application
Server Perf MBean), Performance Servlet, or PMI client API (deprecated).
- JMX Interface
-
JMX interface is part of the J2EE specification and the recommended way
to gather WebSphere Application Server performance data. PMI data can be gathered
from the J2EE managed object MBeans or the WebSphere Application Server PMI
Perf MBean. While the J2EE MBeans provide performance data about the specific
component, the Perf MBean acts as a gateway to the WebSphere Application Server
PMI service, and provides access to the performance data for all the components.
- Performance Servlet
-
Performance Servlet provides a way to use an HTTP request to query the
PMI data for the entire WebSphere Application Server administrative domain.
Since the servlet provides the performance data through HTTP, issues such
as firewalls are trivial to resolve. The performance servlet outputs the
PMI data as an XML document.
- PMI client API (deprecated)
-
PMI client API provides a wrapper class to deliver PMI
data to a client. This API was introduced in WebSphere Application Server,
V4.0 and deprecated in V6.0. The PMI client API uses the JMX infrastructure
and the Perf MBean to retrieve the PMI data. PMI client provides the data
using a WebSphere Application Server-specific data structure that was introduced
in V4.0.
Related concepts
PMI architecture
Performance Monitoring Infrastructure (PMI)
Related tasks
Monitoring overall system health
  Â