Find this tutorial in:
Try the Tutorial
Example showing JMX-managed resources using the MBeanServer API.
Any resource in Resin can be managed by JMX by implementing an MBean interface and by specifying an MBean name. The interface exposes the resource's methods to be managed.
The test resource is identical to the basic example but implements TestAdmin instead of TestMBean. Because the name TestAdmin does not conform to the MBean convention, the web.xml will need to specify the interface explicitly.
The web.xml (or resin.conf) configures the resource with the <resource> tag just as with other resources . The resources is registered as an MBean by specifying an .
MBeanServer is the main JMX interface for managing resources. Although it is less convenient than Resin's proxy interface, it has the advantage of being part of the JMX standard.
Resin stores the MBeanServer it uses for resources in JNDI under the name java:comp/env/jmx/MBeanServer. Applications will use JNDI to get the MBeanServer. This JNDI name is not specified in any standard, so applications might want to encapsulate getting the MBeanServer in a class that can be changed easily.
All management of an MBean uses the MBeanServer and the MBean's ObjectName. In this case, the ObjectName is "example:name=test".
The MBeanServer has three primary management calls: getAttribute, setAttribute, and invoke. This example just uses getAttribute.
Using the MBeanServer interface is compatible with other JMX implementations. The two Resin-dependencies are the configuration and how to obtain the Resin MBeanServer. Different JMX implementations will use a different technique to get the MBeanServer, so it's a good idea to encapsulate getting the MBeanServer in a class that you can change for different implementations.