web server - Borland Technical Publications

JMX support in Partitions
■
■
At Partition startup after all Partition services have loaded their respective modules.
At Partition shutdown before Partition services have unloaded their respective
modules but prior to the services themselves shutting down.
■
At Partition termination after Partition services have been shut down.
Partition Interceptors have a variety of uses, including pre-loading JARs prior to
startup, inserting debugging operations during module loading, or even simple
messaging upon the completion of certain events.
For information about how to implement a Partition Lifecycle Interceptor, see
Chapter 25, “Implementing Partition Interceptors.”
JMX support in Partitions
The Java Management Extensions (JMX) defines an architecture, the design patterns,
the APIs, and the services for application management in the Java programming
language. JMX is used to get and set configuration and performance information, and
send and receive alerts for Java programs. The JMX architecture is composed of
Management Beans (MBeans), a JMX agent, and JMX adaptors.
Each BES Partition hosts a fully functional JMX agent based on MX4J, an open source
implementation of the Sun Microsystems, Inc. Java Management Extensions (JMX) 1.2
specification. BES uses the MX4J HTTP adaptor without modification, but the MX4J
RMI adaptor implementation has been modified to suit the BES Partition in the
following ways:
■
■
Uses the VisiBroker for Java ORB for RMI-IIOP remoting.
RMI Connector is modified to use RMI-IIOP as the underlying transport.
■
The RMIConnectorServer is made available by both the Smart Agent component of
BES and the JMX Service URL.
The goal of the BES JMX implementation is to expose key runtime aspects of a BES
Partition as MBeans. JSR-77 support is available in BES Partitions and has two
fundamental aspects:
1 Instrumentation of the J2EE Server (Partition) following the JSR-77 model.
2 JSR-77 EJB interface to those JMX MBeans.
Currently BES supports (1), but not (2). See “Partition MBeans” on page 23 for a list of
Mbeans provided by Borland for the Partition.
For more details about MX4J see http://mx4j.sourceforge.net, and for the JMX JSR-3
specification see http://cp.org/aboutJava/communityprocess/final/jsr003/index3.html.
Configuring the JMX Agent
The JMX Agent is configured in the jmx section of the partition.xml file. The MBean
Server is enabled by default and starts when the Partition is started. By default the
RMI-IIOP adaptor is enabled and the HTML adaptor is disabled. See Chapter 30,
“Partition XML reference” for more details about the jmx element.
JMX agent configuration can also be accomplished using the Borland Management
Console. See Chapter 2, “Using Partitions” for more information.
22 BES Developer’s Guide