- When to Use Java Management Extensions (JMX)
- Integration of Weblogic with HP OVPM/OVPI
- Custom UDM
- References
- Conclusion
Integration of Weblogic with HP OVPM/OVPI
The OVO architecture follows the Agent-Manager architectural pattern discussed in the previous article of this series. The basic components of the OVO architecture are OVO agents, a management server, and a view component. The agent interacts with the managed resources and is responsible for sending events to the management server. The management server displays the message based on the event captured by the agents. The view component is a display aspect that provides a single view of the enterprise or the managed environment.
The integration of Weblogic and HP OVPM is made possible by configuring a Weblogic Server (WLS) smart plug-in (SPI) from HP for Weblogic. An SPI teaches the OpenView products how to manage the applications, and services. SPIs are the easiest means to extend OpenView management tools.
The SPI for Weblogic allows the defining of a User-Defined Metric (UDM). In addition, the SPI provides access to number of other predefined metrics that can be used for management purposes. For example, developers can use these metrics to get information such as average heap memory utilization, thread pool performance, JDBC connection status and performance, and so on.
A UDM provides a map between the metrics name exposed to HP OpenView and the specific MBean and attribute name. An XML file associated with SPI configuration is used to define User-Defined Metrics. Figure 1 shows the components associated with the integration. In the figure, the display component can be OVPM or OVPI.
Figure 1 Integration of J2EE application in Weblogic using WLS SPI.