Architecture of the JMX Technology:-
The JMX technology can be divided into three parts, as follows:
1 Instrumentation
2 JMX agent
3 Remote management
1 Instrumentation:
Using the JMX technology, you must first instrument the
resources
in the Java programming language. You use Java objects known as
MBeans to
implement the access to the resources' instrumentation. MBeans must follow the
design patterns and interfaces defined in the JMX specification. Doing so
ensures that all MBeans provide managed resource instrumentation in a
standardized way. In addition to standard MBeans, the JMX specification also
defines a special type of MBean called an
MXBean. An MXBean is an MBean
that references only a pre-defined set of data types. Other types of MBean
exist, but this trail will concentrate on standard MBeans and MXBeans.
Once a resource has been instrumented by MBeans, it can be managed through
a
JMX agent. MBeans do not require knowledge of the JMX agent with which
they will operate.
2 JMX Agent:
A JMX technology-based agent (JMX agent) is a standard management agent
that directly
controls resources and makes them available to remote
management applications. JMX agents are usually located on the same machine as
the resources they control, but this arrangement is not a requirement.
The core component of a JMX agent is the
MBean server, a managed
object server in which MBeans are registered. A JMX agent also includes a set of
services to manage MBeans, and at least one communications adaptor or connector
to allow access by a management application.
3 Remote Management:
JMX technology instrumentation can be accessed in many different ways,
either through existing management protocols such as the
Simple Network
Management Protocol (SNMP) or through
proprietary protocols. The
MBean server relies on protocol adaptors and connectors to make a JMX agent
accessible from management applications outside the agent's Java Virtual Machine
(Java VM).
Each adaptor provides a view through a specific protocol of all MBeans
that are registered in the MBean server. For example, an HTML adaptor could
display an MBean in a browser.