It is anticipated that AMQP will grow to global scales of deployment. AMQP will become a critical part of doing business, and consequently the users of it will need to be able to monitor AMQP and manage AMQP deployments within their environment, potentially across several different AMQP implementations.
In order that management does not itself become an avenue for vendor lock-in of the messaging solution, the Management SIG will standardise the critical elements of AMQP's management capabilities.
The purpose of the Management SIG is to:
| First Phase | * Definition of the use cases and requirements * Definition of the architectural model for management * Analysis and selection of a transport protocol (or protocols) for management * Definition of a set of logical data models for broker query and command execution * Definition of a mapping from the logical data model to the physical wire format, and mapping to transport |
| Second Phase | * Definition of a logical data model for management eventing * Definition of mappings to other management protocols (e.g. SNMP, JMX, etc) |
| Third Phase | * Definition of a logical data model for management watchlists |
All Children:
|
Browse Space |
Explore Confluence |
Your Account |
Add Content |
|
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.5 Build:#811 Jul 25, 2007) |