Tuesday June 05, 2007
J2EE Deployment of JMX WS Connector
If you are already evaluating the Early Access 2 of JSR 262, you have perhaps a need to deploy the Connector in your servlet container.
A sample, located in samples/servletdeployment directory, shows you how to achieve such deployment. The provided example shows how to deploy the JSR262 JAX-WS Endpoint
com.sun.jmx.remote.ws.wsman.JMXWSManServiceEndpoint inside a JAX-WS compliant servlet container. When created, the endpoint gets a reference to the platform MBeanServer (thanks to java.lang.management.ManagementFactory.getPlatformMBeanServer())If the MBeans you want to manage are registered inside the platform MBeanServer, you can reuse this sample code. Registering MBeans in the platform MBeanServer is something that we encourage.
If you want to attach the connector to another MBeanServer, then you need to subclass
JMXWSManServiceEndpoint and provide your own MBeanServer.
Extending JMXWSManServiceEndpoint JAX-WS endpoint
When extending an annotated class (JMXWSManServiceEndpoint JAX-WS endpoint is annotated), the extended class doesn't inherite from the mother class annotations, you need to re-annotate the extended class.When deploying in J2EE, no JMXServiceURL is provided to the connector (as opposite to the JMX J2SE way of deploying a Connector). You need to provide to the Connector the URL on which it has been deployed. This is done by calling
setURL on JMXWSManServiceEndpoint class. This URL is used when translating from MBean ObjectName to WS-Addressing EPR.
Extended class
The following sample code is a ready to deploy extended class that gets a reference to the first MBeanServer found thanks to thejavax.management.MBeanServerFactory class. The URL on which the endpoint has been deployed is hard coded. You can easily externalize it, for example read it from a property file.
import com.sun.jmx.remote.ws.api.JMXWSManDispatcher;
import com.sun.jmx.remote.ws.api.JMXWSManServiceEndpoint;
import javax.xml.ws.WebServiceContext;
import javax.annotation.Resource;
import javax.management.*;
@javax.xml.ws.WebServiceProvider
@javax.xml.ws.ServiceMode(value=javax.xml.ws.Service.Mode.MESSAGE)
public class ExtendedEndpoint extends JMXWSManServiceEndpoint {
@Resource
private WebServiceContext context;
public ExtendedEndpoint() throws Exception {
super(new JMXWSManDispatcher(null,
(MBeanServer)MBeanServerFactory.findMBeanServer(null).get(0)));
}
protected WebServiceContext getWebServiceContext() {
return context;
}
}
Packaging the connector
You simply need to update the endpoint implementation in the sun-jaxws.xml file and repackage the extended class in a war file similar to the sample.sun-jaxws.xml file
<?xml version="1.0" encoding="UTF-8"?>
< endpoints
xmlns="http://java.sun.com/xml/ns/jax-ws/ri/runtime"
version="2.0">
< endpoint
name="JMXWSManEndpoint"
implementation="ExtendedEndpoint"
service="{http://jsr262.dev.java.net/jmxconnector/wsdl}JMXConnectorService"
port="{http://jsr262.dev.java.net/jmxconnector/wsdl}JMXConnectorPort"
url-pattern="/jmxws"
binding="http://www.w3.org/2003/05/soap/bindings/HTTP/">
</endpoint>
</endpoints>
Conclusion
The simpler way to deploy the Connector is by using the JMXConnectorServerFactory class. This will answer your needs when you want to take benefit of the JAX-WS http server. Direct JAX-WS endpoint deployment is the other way when reusing an existing infrastructure.Jean-François
Posted by jeanfrancoisdenise ( Jun 05 2007, 11:48:45 PM GMT+02:00 ) Permalink Comments [1]
Post a Comment:
Comments are closed for this entry.
This is a personal weblog, I do not speak for my employer.
Posted by JMX, SNMP, Java, etc... on June 06, 2007 at 11:16 AM GMT+02:00 #