JMX Usage and Integration of Weblogic with HP OpenView Performance Manager/Performance Insight
- When to Use Java Management Extensions (JMX)
- Integration of Weblogic with HP OVPM/OVPI
- Custom UDM
- References
- Conclusion
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
When should you use Java Management Extensions (JMX)? This article discusses when to use JMX and shows you what you need to collect performance metrics through JMX (MBeans) registered with Weblogic MBean Server by using HP OpenView Performance Manager (OVPM). (The steps are identical, from a development perspective, to OpenView Performance Insight [OVPI]). The MBean used here is the PerformanceMetricsMBean that we developed in our previous article in this series, "Weblogic Application Performance Metrics Collection Using JMX and OpenView Performance Manager/Performance Insight."
When to Use Java Management Extensions (JMX)
Without JMX, you have to build a custom module for every application that needs to be managed. This module integrates the application management information into the management system. One of the goals of JMX was to provide sufficient information to the management system so manageability can be generated or provided generically without the need to write custom integration modules.
JMX is a model-less management architecture, and sufficient information is provided to a management system by supplying metadata through MBeanInfo object for every MBean. The management system adaptors and tools can use this metadata information to create integration modules.
Using JMX enables Java applications to be managed without heavy investment by integrating existing management solutions as JMX makes management data available via a choice of protocols (SNMP, HTTP, SOAP, and so on). JMX provides an easy-to-use Java API and a scaleable management architecture.