Apache Qpid : QMan Components View
This page last changed on Mar 06, 2009 by agazzarini.
Components ViewAt package level, QMan is composed by 4 core packages illustrated in the picture below : Package configurationThis package contains all configuration entities / items shared between all QMan components. ConfiguratorWhen QMan starts, this component is responsible to build the configuration for that instance. As you can see it uses several built-in builders in order to create and populate the configuration instance. ConfigurationEncapsulates a configuration for a QMan instance. Note that this is a singleton because it must be accessed from everywhere inside QMan sub-modules. ParserActive participants of the configuration build process. Basically they are responsible to parse a specific section of the (optional) qman-configuration file that is given at QMan startup. At the moment we have two implementantion of this interface :
WorkerManagerConfigurationDataA value object encapsulating configuration data for the work manager. BrokerConfigurationDataA value object encapsulating connection data of a remote broker. AccessModesA map associating a code with an access mode. At the moment we have three access modes :
Message HandlersEach time a message is received from a remote broker there will be a specific message handler that is responsible for processing that message. Package domainPackage jmxContains 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. Package wsdmComponents that belong to this package enable QMan interfaces to be exposed using WS-DM / HTTP. As part of that, this package contains
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). QManLifecycleManagerSimply speaking, we could say that the whole WSDM Layer acts as a facade of the JMX Adapter, so it should be able to control the lifecycle of a that adapter. This component is a web component that (as the name suggests) provides a lifecycle management (startup & shutdown) of a JMX adapter instance. WsDmAdapterAn HTTP Servlet that listens for incoming WS-DM / HTTP requests and dispatches those requests to the appropriate handler. QManA front controller of the JMX instrumentation layer exposed itself for management (as an MBean). QManWsResourceQMan object representation of a WS-Resource. A WS-Resource is a composition of a management resource and a Web service through which the resource can be accessed. QManWsAdapterA static WS-Resource that acts as a controller / facade of QMan WS-DM management domain model. Basically it provides the following features :
SubscriptionManagerA WS-Resource that enables QMan notifications. It provides operations that allow a requestor to query and manipulate subscription resources that it manages. For example it is possible (on requestor side) to pause and resume a subscription. MBeanWSResourceThis is the interface that all QMan WS-Resources have. Although a concrete implementation of this interface is built at runtime, it indicates that the resources will have a common set of features (attribute retrieveal, operation invocation). Other WS interfacesThe other interfaces on the diagram simply enumerates all the WS-DM interfaces that will be implemented by the QMan WS-Resources. More information about those interfaces are found here . ![]() ![]() ![]() |
![]() |
Document generated by Confluence on May 26, 2010 10:33 |