Java Reference
In-Depth Information
9.6 Summary
Previous chapters made it clear how
JMX
uses protocol adapters and connectors
to provide connectivity to
JMX
agents through all manner of technologies and
protocols. This chapter covered the
RMI
connector more thoroughly, discussed
SNMP
, and showed you how to write a Jini connector and a
TCP
adapter.
The
RMI
connector is contributed to developers in Sun Microsystems'
JMX
Reference Implementation. It lets you connect to remote
JMX
agents using Java
RMI
. In addition, it provides excellent handling of remote notification delivery
and heartbeat functionality.
The Jini connector you wrote took the
RMI
connector one step further by
allowing you to connect to a
JMX
agent using the Jini network technology. The
connector still operates over Java
RMI
, but clients do not have to know the
address of a potential
JMX
agent. Using the Jini discovery mechanism, you were
able to provide an agent discovery capability to remote clients.
Finally, you created a
TCP
adapter to provide access to
JMX
agents from non-
Java clients. Even though the
TCP
adapter is limited by its inability to translate
complex objects to simple commands, it does provide the core functionality of a
JMX
agent to
TCP
clients. In fact, the
TCP
adapter is much like the
HTML
adapter.
Chapter 9 not only provided you with the examples for agent connectivity,
it also showed you some guidelines for writing your own custom classes in order
to provide connectivity for other technologies or protocols that you have in
your environment.
Agent services provide important functionality to every
JMX
agent. Chapter 10
covers the first of four agent services that are present in every
JMX
-compliant
agent: the M-let service, which is used to load MBeans from remote locations
outside an agent's codebase.
