This page last changed on Feb 26, 2009 by agazzarini.

JMX Interface Specification

This section contains QMan JMX Interface Specification.
Note that what is explained in this section refers to what is commonly addressed as "Instrumentantion Layer".
That means the "Agent Layer" is not part of QMan and therefore it relies on standard JMX API.
So, strictly speaking, the described interface in not directly exposed but rather intermediated by the agent layer and specifically by the MBeanServer.
The following table describes the three entity types that are part of QMan management domain model.

Resource Type
Description
Multiplicity
QMan MBean QMan is exposed itself as an MBean. 1
Object MBean
QMan JMX representation of a Qpid domain object exposed for management / monitoring.
0...*
Event MBean
QMan JMX representation of a Qpid domain event exposed for monitoring.
0...*
Document generated by Confluence on May 26, 2010 10:33