[
https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633926#action_12633926
]
Ted Ross commented on QPID-1284:
--------------------------------
Andrea,
For method calls, use a routing key of "agent.0". Here's the list of items to
be encoded:
Header (opcode='M')
ObjectId of target object (128 bits)
Package name (str8)
Class name (str8)
Class hash (bin128)
Method name (str8) [as defined in the schema]
Now encode all input ("I") and i/o (IO) arguments in the order in which they
are defined in the schema. (i.e. make one pass over the argument list and
encode arguments that are either input or inptu/output).
The response will be encoded thus:
Header (opcode='m')
Status code (uint32)
Status text (str8)
all output (O) and i/o (IO) arguments in the order in which they appear in the
schema.
-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, QpidClass.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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
