Hi Bryan, QMan is basically exposing the management interface of a (QMF management-enabled) broker. There are two version of QMan :
1) JMX Adapter : exposes the management interface of the broker as JMX MBean. you can see those MBeans using JConsole or in alternative embedding it into an Application Server with a JMX console (e.g. JBoss, WebLogic, etc...). You can also write your own console using QMan API. In any case for this scenario the client is supposed to be java based. 2) WS-DM Adapter : exposes the management interface as WS-Resource and enables interaction using WS-DM. This can be used : - as a standalone module ($QMAN_HOME/bin/qman-wsdm-start.sh) because it has an embedded Jetty Web Server; - as a deployable web application module (war). In this case you must deploy it on an Application Server; The web module already has an integrated graphical console (as part of the web application). Once you started it point your browser to http:// <host>:<port>/qman/console The difference with the previous scenario is that the requestor (client) could be any WS-DM enabled client (your own management application or for example HP OpenView) This image http://qpid.apache.org/qman-system-overview.html <http://qpid.apache.org/qman-system-overview.html>will give you an immediate overview of what I told you above. Regards, Andrea 2009/6/10 Bryan Kearney <[email protected]> > Andrea Gazzarini wrote: > >> Hi Bryan, sorry for delay,I developed QMan, how can I help you? >> Regards, >> Andrea >> > > Andrea: > > I just wanted to make sure I understood all the bits. QMan's goal is to > manage the broker? So, there is still need for Console and Agent code to > embed in a Java container. Is that correct? > > > -- bk > > >> > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > >
