JMX connectors

Hi Jahnvi,

The JMX RMI Connector is the only standard connector that an implementation of the

JMX Remote API is required to have. Today it is the only connector which is included in the

JDK (JDK 5 and later).

There is also JSR 262 which defines a Web-Services Connector for JMX. One of

the advantages of JSR 262 connector is that it's based on HTTP, and therefore is

more firewall friendly. Another advantage is that it will make it possible for non

Java application to interact with JMX instrumentation. However, this connector is

still under development. It's probably not going to be as fast as the RMI connector

either.

The JMX Remote API spec also defines a TCP based connector - the JMXMP connector

is optional, and is not part of the JDK.

You will also probably find a number of proprietary JMX Connectors (like MX4J SOAP

connector).

As long as your client is written in Java, which connector implementation you use

should not matter much. Since the RMI is the only connector included in the JDK

platform, is well tested, and is satisfactory for most use cases I would recommend

using that one.

If you're setting up a mangement infrastructure in an environment with constraining

firewall policy you might consider later switching to the Web Services connector when its

final implementation is available.

Adaptors are another kind of beasts, and I am assuming that you probably don't need these.

See http://blogs.sun.com/jmxetc/entry/what_is_jmx

for more info.

Hope this helps,

-- daniel

JMX, SNMP, Java, etc...

http://blogs.sun.com/jmxetc

dfuchsa at 2007-7-8 2:15:45 >