Page History

...

Candidates: Rahul Metha

Project Goal: Create a dynamic bridge from between AMQP-mgmt protocol to JMX to facilitate std management console integrationJMX and WS-DM

Mentor: Arnaud

Project Description:

Project is to create a process will receive management Data through the AMQP mgmt protocol and translate those into WS-DM This will allow the C++ broker to also be hooked into any WS-DM console and allow for all the instrumentation data to be read, all the methods to be invoked, and the configuration to be updated through standard WS-DM console to expose the AMQP JMX-instrumented applications (Java broker and JMX/C++ management bridge) using MS-DM interfaces. Referring to the JMX architecture, this mapping should be addressed through a JMX-WS-DM connector. This will allow any qpid broker to be hooked into industry standard management product line like BMC, Tivoli, etc.

Note that all the schema is dynamic, so the bridge need to configure itself at runtime, so this service should derive it's behavior from the schema provided to it.

AMQP mgmt side protocol current qpid Java broker JMX can be found here: http://cwiki.apache.org/qpid/jmx-management-design-notesconsole.html^{Image Modified}

To play with it, you should build the C++ broker
./bootstrap
./configure
make

on linux, the to run the cmd line mgmt set the PYTHONPATH and run it from mgnt-cli

You should pretty quickly see how the objects get dynamically build and how they are layed out, these can then quite simple be dynamically mapped into the WS-DM intefaces.

Java broker

Implementation language is Java. Implementation language is the choice of the implementor (suggested languages are Python or Java)

JMX Cli

Candidates: Lahiru Gunathilaka

...