[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge

["Andrea Gazzarini (JIRA)" <qp...@incubator.apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631773#action_12631773 ] 

Andrea Gazzarini commented on QPID-1284:
----------------------------------------

*** status of the work ***

I developed a first prototype which is able to interface with a M2.1 C++ broker.(the version installed with yum install qpidd on Fedora) I'm going to preparetyhe code for submit .
Now I built the qpid c++ broker from the trunk and it seems that it's not working because something has changed in the 'c' ContentIndication Message. I'm trying to investigate...  
I'm also preparing some UML diagrams to explain what I've done and what I should do on this component.

- Gazza - 

> 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
>
> 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.