WAS v8.5 > Monitoring > Monitoring overall system health > PMIPMI data page
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 WAS performance data. PMI data can be gathered from the J2EE managed object MBeans or the WAS PMI Perf MBean. While the J2EE MBeans provide performance data about the specific component, the Perf MBean acts as a gateway to the WAS 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 WAS 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. The PMI client API uses the JMX infrastructure and the Perf MBean to retrieve the PMI data. PMI client provides the data using a WAS-specific data structure.
- PMI client API provides a wrapper class to deliver PMI data to a client. The PMI client API uses the JMX infrastructure and the Perf MBean to retrieve the PMI data. PMI client provides the data using a WAS-specific data structure.
Related concepts:
PMI architecture
PMI
Related
Monitoring overall system health