JSR-160 Connectors - Java-Springs

For remote access, Spring JMX module offers two FactoryBean implementations inside the org.springframework.jmx.support package for creating both server- and client-side connectors.

Server-side Connectors
To have Spring JMX create, start and expose a JSR-160 JMXConnectorServer use the following configuration:

<bean id="serverConnector" class="org.springframework
.jmx.support.ConnectorServerFactoryBean"/>

By default ConnectorServerFactoryBean creates a JMXConnectorServer bound to "service:jmx:jmxmp://localhost:9875". The serverConnector bean thus exposes the local MBeanServer to clients through the JMXMP protocol on localhost, port 9875. Note that the JMXMP protocol is marked as optional by the JSR 160 specification: currently, the main open-source JMX implementation, MX4J, and the one provided with J2SE 5.0 do not support JMXMP.

To specify another URL and register the JMXConnectorServer itself with the MBeanServer use the serviceUrl and ObjectName properties respectively:

<bean id="serverConnector"
class="org.springframework.jmx.support.
ConnectorServerFactoryBean">
<property name="objectName"value=
"connector:name=rmi"/>
<property name="serviceUrl"
value="service:jmx:rmi://localhost/
jndi/rmi://localhost:1099/myconnector"/>
</bean>

If the ObjectName property is set Spring will automatically register your connector with the MBeanServer under that ObjectName. The example below shows the full set of parameters which you can pass to the ConnectorServerFactoryBean when creating a JMXConnector:

<bean id="serverConnector"
class="org.springframework.jmx.support.
ConnectorServerFactoryBean">
<property name="objectName"value=
"connector:name=iiop"/>
<property name="serviceUrl"
value="service:jmx:iiop://localhost/jndi/iiop://
localhost:900/myconnector"/>
<property name="threaded"value=
"true"/>
<property name="daemon"value=
"true"/>
<property name="environment">
<map>
<entry key="someKey"value="
someValue"/>
</map>
</property>
</bean>

Note that when using a RMI-based connector you need the lookup service (tnameserv or rmiregistry) to be started in order for the name registration to complete. If you are using Spring to export remote services for you via RMI, then Spring will already have constructed an RMI registry. If not, you can easily start a registry using the following snippet of configuration:

<bean id="registry"class="org.
springframework.remoting.rmi.RmiRegistryFactoryBean">
<property name="port"value="1099"/>
</bean>

Client-side Connectors
To create an MBeanServerConnection to a remote JSR-160 enabled MBeanServer use theMBeanServerConnectionFactoryBean as shown below:

<bean id="clientConnector"class="
org.springframework.jmx.support.MBeanServerConnectionFactoryBean">
<property name="serviceUrl"value="
;service:jmx:rmi://localhost:9875"/>
</bean>

JMX over Burlap/Hessian/SOAP
JSR-160 permits extensions to the way in which communication is done between the client and the server.The examples above are using the mandatory RMI-based implementation required by the JSR-160 specification (IIOP and JRMP) and the (optional) JMXMP. By using other providers or JMX implementations (such as MX4J) you can take advantage of protocols like SOAP, Hessian, Burlap over simple HTTP or SSL and others:

<bean id="serverConnector"
class="org.springframework.jmx.support.
ConnectorServerFactoryBean">
<property name="objectName"value
="connector:name=burlap"/>
<property name="serviceUrl"value=
"service:jmx:burlap://localhost:9874"/>
</bean>

In the case of the above example, MX4J 3.0.0 was used; see the official MX4J documentation for more information.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

Java-Springs Topics