THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
QMan : Qpid Management Bridge
QMan is a management bridge for Qpid. It allows external clients to manage and monitor one or more Qpid brokers.
Please note: All WS-DM related concerns have to be considered part of M5 release.
QMan exposes the broker management interfaces using Java Management Extensions (JMX) and / or OASIS Web Services Distributed Management (WSDM). While the first one is supposed to be used by java based clients only the latter is an interoperable protocol that enables management clients to access and receive notifications of management-enabled resources using Web Services.
QMan can be easily integrated in your preexisting system in different ways :
- As a standalone application : in this case it runs as a server. More specifically it enables communication via RMI (for JMX) or via HTTP (for WS-DM); Note that when the WS-DM adapter is used the JMX interface is not exposed;
- As a deployable unit : it is also available as a standard Java web application (war); This is useful when there's a preexisting Application Server in your environment and you don't want start another additional server in order to run QMan.
User Documentation
With "User Documentation" we mean all information that you need to know in order to use QMan from a user perspective. Those information include :
The first one is a brief quick start guide in order to get QMan up and running; the User Guide describes QMan module with its features from a functional perspective.If you don't know where to start from, please consider having a look at the User Guide first in order to get a big picture about how things are working.
Technical Documentation
If you are interested in technical details about QMan and related technologies this is a good starting point. In general this section provides information about QMan design, interfaces, patterns and so on...
- QMan design
- JMX interface
- WS-DM interface Specification