The JMX architecture is multilayered, as shown in the following diagram:
Distributed Services level |
Web browser |
Other |
JMX-compliant management applications |
Proprietary management applications |
Agent level |
Protocol adapters
|
Connectors.. |
JMX manager |
..
|
MBeanServer... |
...
|
Agent Services |
Instrumentation level |
Instrumentation strategy (MQe
JMX implementation) |
Application Resources |
The scope of the MQe JMX implementation is limited to the Instrumentation
level and Instrumentation strategy (MQe JMX implementation).
The following are explanations of some of the terms used in the diagram:
- Distributed services level
- The distributed services level of the JMX architecture contains the middleware
that connects agents to management applications.
- Agent level
- The agent level of the JMX architecture provides a registry for handling
the manageable resources, called the MBeanServer, as well as several agent
services which are themselves MBeans.
- JMX agent
- A JMX agent is a combination of an instance of the MBeanServer, its registered
MBeans and any agent services within a single JVM.
- Managed Beans (MBeans)
- Resources instrumented according to the rules of the JMX specification.
There are two main categories of MBeans:
- Standard MBeans implement their own interface, and are static.
- Dynamic MBeans (of which there are several sub-categories) implement
a JMX interface called DynamicMBean. This interface contains methods that
allow the management interface of the managed resource to be discovered at
run-time.
- Instrumentation level
- The instrumentation level of the JMX architecture is the level at which
resources to be managed are instrumented for JMX management. To make this
possible, the resources must be instrumented as MBeans.
- Resource
- Any entity that needs to be monitored or controlled by a management application.
In the context of this implementation, MQe queue managers, queues, and so
on, are all resources.