|
|
In previous releases of AquaLogic Service Bus, run-time service-monitoring data was only available through the Monitoring Dashboard of the AquaLogic Service Bus console. It was not possible for clients to programmatically access and consume monitoring data.
The JMX Monitoring API in AquaLogic Service Bus provides external access to monitoring data. Java Management Extensions (JMX) technology was used for the implementation, as it is a public standard that meets the implementation requirements.
The primary purpose of the JMX Monitoring API is to provide efficient, lower-level APIs supporting bulk operations. It does this using JMX as a transport. This API is not a high-level API compatible with JMX-based tools. However, if you are developing client software, you may want to develop high-level JMX APIs that support JMX-based tooling.
The JMX monitoring API makes use of JMX as a transport only.
It exposes a public MBean to provide all the required operations to get monitoring data (statistical information) for any monitored service and its components.
It also exposes a set of public POJO objects required to carry out operations provided by the MBean.
There is no need for third-party client software to know the intricacies of the hierarchy inherent in the statistical information stored in the AquaLogic Service Bus monitoring system.
Using these APIs, customers can integrate their monitoring/management systems with AquaLogic Service Bus to do the following:
For more information about AquaLogic Service Bus 3.0, see BEA AquaLogic Service Bus 3.0.
For basic concepts and terminology, see AquaLogic Service Bus Concepts and Architecture.
|