Andrea Gazzarini wrote:
Hi all, another piece of ws-dm info concerning notifications & events :
While JMX Notification listener is a normal java class running on a
standalone application, WS-DM event listeners must be a valid web service
endpoint (not a standalone application) so I think that in order to
demonstrate the (future) capabilities of the WS-DM adapter we could create a
management console that is a web application able to connect with QMan (and
therefore to a Qpid management enabled) via WS-DM. So the final scenario
will be :
Mgmt Console / Mgmt client (ex: HP Openview) --(wsdm)--> WS-DM Adapter
--(jmx)--> QMan --(amqp)--> Qpid
What do you think? It should be great for example to develop that management
console using Ajax in order to have the user interface automatically
refreshed after subscribed notifications...
...but before of that the WS-DM adapter must be completed :)
Best Regards,
Andrea
Andrea,
I think the value of the WS-DM Adapter is so that HP Openview, BMC
patrol etc can be plugged
into a Qpid QMF install. i.e. WS-DM provides the way to integrate with
the big brand name
consoles
However, in writing a console specific to Qpid I would not go via WS-DM,
but rather directly from
the QMFC interfaces. Two examples are such consoles done from QMF are
oVirt (done in Ruby) and
the Red Hat MRG console done in Python. Both of these are web based Ajax
consoles.
I can post some screen shots on the wiki, and if you want to hack in
that area shout.
Carl.
