[
https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631823#action_12631823
]
Ted Ross commented on QPID-1284:
--------------------------------
Gazza,
A few quick notes...
1) The "management design notes" wiki page is no longer being updated. It
represents the state of the code in the M3 release.
2) A new page has been created
(http://cwiki.apache.org/confluence/display/qpid/Qpid+Management+Framework) for
the ongoing effort. Lots of details need to be filled in.
3) After a quick look at the QMan code (which looks very neat by the way), I
think the main issue you are having with the trunk is that the objectId has
been expanded from 64-bits to 128-bits. Other protocol updates have occurred
in the method and event area but those don't yet affect you (yet).
4) Another feature your code doesn't support is optional properties. Search
for "optional properties" in the M3 management design notes for details.
-Ted
> QMan : Qpid JMX Management Bridge
> ---------------------------------
>
> Key: QPID-1284
> URL: https://issues.apache.org/jira/browse/QPID-1284
> Project: Qpid
> Issue Type: New Feature
> Affects Versions: M3
> Environment: J2SE 5, any OS that is supporting Java
> Reporter: Andrea Gazzarini
> Attachments: DomainModel.jpg, QMan.jar
>
>
> QMan is an application used for exposing via JMX the management domain model
> of one or more remote brokers.
> Capabilities (the list is not complete) :
> - Operates from a formally defined management schema;
> - Uses the AMQP protocol and its type system for communicating with remote
> brokers;
> - Exposes via JMX the remote broker domain model: that means for each
> connected broker QMan lets you see its domain model entities according to
> their schema (attribute, methods, statistics and events). In addition, lets
> you invoke operations on those entities.
> - Multi broker management;
> - It doesn't have prior knowledge of the management model of the system under
> management. no definition is hard-coded and entity definitions (schema) are
> requested and built "on demand";
> - Namespace separation between brokers : each connected broker can have a
> different schema.
> - JMX interface : QMan is itself a Management Bean and using JMX it exposes
> its public interface (for example, to connect with a new broker). So at the
> end it should be exposed via WS-DM, SMTP, RMI, etc...
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
