web server - Borland Technical Publications

JMX support in Partitions
Figure 3.2
Partition MBeans
The MBeans are available only if you enable the JMX feature in the Performance
Tuning wizard. See Chapter 2, “Using Partitions” for information on how to enable the
JMX feature. The level of information that is provided in the MBeans depends on the
statistics level you set in the Performance Tuning Wizard. Complete JSR-77 statistics
will be available only if you select the statistics level as “maximum”. You will get only a
subset of the JSR-77 statistics if you select “medium” or “minimum”.
Deploying custom MBeans
To deploy custom MBeans:
1 Decide where to initialize your MBeans (possible places include a servlet or Startup
class).
2 Add the JNDI lookup code to locate the MBeanServer.
There is currently no standard way for the application to locate the JMX agent
(server) in an application server infrastructure. So, what you should do is follow the
model that is similar to the J2EE approach of looking up the ORB, UserTransaction,
etc. that is shown in the code snippet below.
Note that JMX agent is a server side feature, and the lookup operation in the client
VM will not be able to find a pointer to the server instance as the server is only
initialized in the server VM. A client will need to use the RMI-IIOP connection to
connect to a remote JMX agent.
3 Register the MBeans.
Once the MBean server is located, the registration step is just a normal process.
Note that your MBeans have to be in the classpath when you are doing these steps.
Also note that depending upon where you end up having your JMX code, you may
want to clean up your MBeans (unregister them) when your module is unloaded. For
example if your MBeans were registered in the Startup class, you may want to
unregister your MBeans in a Shutdown class.
24 BES Developer’s Guide