THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The extensibility requirement introduces complexity to the management protocol that is unnecessary and undesirable for the user/developer that wishes only to manage QPID message brokers. For this reason, the protocol is partitioned into two parts: The basic protocol, which contains only the capability to manage a single broker; and the extended protocol, which provides the hooks for managing an extended set of components. A management console can be implemented using only the basic protocol if the extended capabilities are not needed.
Architectural Framework
There are two primary interfaces defined in the management architecture:
- The Management Console Interface is used by management clients (CLIs, GUIs, console servers, etc.) to remotely access management data.
- The Extension Interface is used by software components (not necessarily related to the QPID infrastructure) to provide access to their managed objects.
| No Format |
|---|
+---------+ +---------+ +---------+
| | | | | |
| CLI/GUI | | Console |<======>| CLI/GUI |
| | | Server | | |
+---------+ | | +---------+
^ +---------+
| ^
| |
v v
+---------------------------------+
| |
| Managed QPID Infrastructure |
| |
+---------------------------------+
^
|
v
+------------+
| |-+
| Management | |-+
| Extensions | | |
| | | |
+------------+ | |
+------------+ |
+------------+
|
Both management interfaces are based on the AMQP protocol and its type system.Architectural Framework
The Management Exchange
The management exchange (called "qpid.management" currently) is a special type of exchange used for remote management access to the Qpid broker. The management exchange is an extension of the standard "Topic" exchange. It behaves like a topic exchange with the following exceptions:
...