web server - Borland Technical Publications

JMX support in Partitions
Partition monitoring
Note
Note
A JMX agent is embedded in each Partition, along with the HTTP and RMI-IIOP
adaptors, to enable Partition monitoring with a JMX client. This means it is possible for
a JMX-enabled client (such as the MC4J Management Console, provided with your
BES installation) to automatically detect these MBeans and plot graphs for the
changing values. For more information about using the MC4J Management Console
see Chapter 13, “Using the JMX console.”
When you right-click on a partition name, the Launch JMX Console... menu option will
be enabled only if you have enabled the JMX agent in the Performance Tuning Wizard.
If you enable the http.adaptor and xslt.processor elements in partition.xml, you can
also use a Web browser to monitor the Partition by way of the HTTP adaptor. The
default location of the HTTP adaptor is http://localhost:8082. See Chapter 30, “Partition
XML reference” for information about configuring the HTTP adaptor.
In this release the emphasis is on monitoring rather than actively managing the
Partition using JMX. It is recommended that you continue using the Borland
Management Console to manage (stop, start) Partitions. See Chapter 2, “Using
Partitions” for more information.
Partition MBeans
This section describes the MBeans provided by Borland for the Partition. If you want to
deploy your own MBeans see “Deploying custom MBeans” on page 24.
The naming convention for the MBeans is from JSR-77. Please refer to JSR-77 section
3.1.1 for a complete description of this naming convention.
The following illustration shows you a high level overview of the MBeans implemented
for the BES Partition.
Chapter 3: Partitions 23