You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2016/12/09 20:19:58 UTC

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

     [ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Ross closed QPID-1284.
-----------------------------

> 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
>            Assignee: Arnaud Simon
>         Attachments: DomainModel.jpg, Invokes an operation.jpg, QMan.jar, QpidClass.jpg, actors.jpg, class_definition_building.jpg, commons-pool-1.4.jar, configuration_domain_model.jpg, estabilish_initial_connection.jpg, management_message.jpg, message_processing.jpg, qman_14102008_latest.patch, qman_patch, qman_patch_08102008, qman_patch_14102008, qman_predefined_handlers_patch, qman_test_cases_patch, qman_test_cases_patch_08102008, qpid_patch_under_management_folder_12102008, use_cases.jpg
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org