To make a JMX agent accessible from management applications outside the agent's JVM
MBean server relies on protocol adaptors and connectors. Basically adaptors
provide a view through a specific protocol for all MBeans registered in the
MBean server (e.g. an HTML adaptor could display an MBean in a Web
browser). Manager-side interface provided by the connectors that handles the
communication between manager and JMX agent. When a remote management
application uses such interface, it connect to a JMX agent transparently
through the network regardless of the protocol.
To remote applications by using Remote Method Invocation (RMI) JMX technology exports JMX API instrumentation.
It also defines an optional protocol based
directly on TCP sockets called the JMX Messaging Protocol (JMXMP). But this this protocol is not supported in J2SE 5.0.
The JMX Remote API 1.0 (JSR 160) specification describes how to advertise and
find JMX agents using existing discovery and lookup infrastructures. In other
way the specification does not define its own discovery and lookup service.
Using existing discovery and lookup services is optional; you may encode the
address of your JMX API agents in the form of URLs and make these URLs available
to the manager.
Example 4 shows an example of using the RMI connector, which is a slight modification of Example 3.