Components View

At package level, QMan is composed by 4 core packages illustrated in the picture below :

Package configuration

This package contains all configuration entities / items shared between all QMan components.
Those includes both configuration items that are directly under the user control and not-public items used internally to configurate (sub) components.
As you can see, the configuration package is a central grouping of components that serve the remaining three modules.

Package domain

Package jmx

Contains all services that are part of QMan JMX adapter. A special note should be done for this package because even from the picture is not clear, the JMX core could be used independently from the WSDM adapter.
That means this package contains all services and interfaces needed for expose a Qpid management domain model using JMX.
That fits a management scenario where there's a java agent layer that wants to monitor / instrument / manage one or more remote brokers.
Each managed entity will have its own JMX representation as an MBean with common and specific features (depending on the resource type).
JMX interfaces and entities are detailed here

Package wsdm

Components that belong to this package enable QMan interfaces to be exposed using WS-DM / HTTP. As part of that, this package contains

• standard JEE Web components (Servlets and Context Listeners).
• WS-DM specific components

Note that this is an additional layer over the previous JMX core so the basically the same considerations apply management resources (in this case we call them WS-Resources).

WSDM Components Diagram (click to toggle)

QManLifecycleManager

WsDmAdapter

QMan

QManWsResource

QManWsAdapter

SubscriptionManager

MBeanWSResource

Other WS interfaces

More information about WS-DM interface specification are here .