A comprehensive set of Java Management Extensions (JMX) MBeans
that expose broker resources using the JMX API

Support for the Java ES Monitoring Framework

The following subsections describe these components.

Figure 3–3 Monitoring Service Support

Metrics Generator

The metrics generator provides information about broker activity, such
as message flow in and out of the broker, the number of messages in broker
memory and the memory they consume, the number of open connections, and the
number of threads being used.

You can set broker properties to turn the generation of metric data
on and off, and to specify how frequently metrics reports are generated.

Logger

The Message Queue logger takes information generated by broker code
and the metrics generator and writes that information to standard output (the
console), to a log file, and, on SolarisTM platforms,
to the syslog daemon process in case of errors.

You can set broker properties to specify the type of information gathered
by the logger as well as the type written to each of the output channels.
In the case of a log file, you can also specify the point at which the log
file is closed and output is rolled over to a new file. Once the log file
reaches a specified size or age, it is saved and a new log file created.

Metrics Message Producer

The metrics message producer shown in Figure 3–3 receives information from the metrics generator at regular intervals
and writes the information into messages, which it then sends to one of a
number of metric topic destinations, depending on the type of metric information
contained in the message.

JMX MBeans

The broker implements a comprehensive set of Java Management Extensions
(JMX) MBeans that represent the broker's manageable resources. Using the JMX
API, you can access these MBeans to perform broker configuration and monitoring
operations programmatically from within a Java application.

In this way, the MBeans provide a Java application access to data values
representing static or dynamic properties of a broker, connection, destination,
or other resource. The application can also receive notifications of state
changes or other significant events affecting the resource.

Java ES Monitoring Framework Support

Message Queue supports the Sun Java Enterprise System (Java ES) Monitoring
Framework, which allows Java Enterprise System components to be monitored
using a common graphical interface. This interface is implemented by a web-based
console called the Sun Java System Monitoring Console. If you are running
Message Queue along with other Java ES components, you might find it more
convenient to use a single interface to manage all these components.

The Java ES monitoring framework defines a common data model (CMM) to
be used by all Java ES component products. This model enables a centralized
and uniform view of all Java ES components. Message Queue exposes the following
objects to the Java ES monitoring framework:

the installed product

the broker instance name

the broker port mapper

each connection service

each physical destination

the persistent store

the user repository

Each one of these objects is mapped to a CMM object whose attributes
can be monitored using the Java ES monitoring console. At runtime, administrators
can use the console to view performance statistics, create rules to monitor
automatically, and acknowledge alarms. For detailed information about the
mapping of Message Queue objects to CMM objects, see the Sun Java
Enterprise System Monitoring Guide.

Using the Java ES Monitoring Framework will not impact broker performance
because all the work of gathering metrics is done by the monitoring framework,
which pulls data from the broker's existing monitoring data infrastructure.