correct me if I'm wrong
rhq consists of a server and agent component. To integrate you would write an agent plugin which could interact with the JBM Management API directly. This could be a totally separate project and wouldn't directly add any dependencies to JBM. Since it's added to the rhq agent which runs in a separate JVM.
The rhq agent communicates with the server via JBoss Remoting but has a web-app to interact with it. You would probably need to customize the web-app to add support for JBM management functions. This is the part I'm unfamiliar with.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130566#4130566
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130566
"mazz(a)jboss.com" wrote : (side note: the comm layer between RHQ's server and agent has JBoss/Remoting 2 under the covers):
I would be interested in knowing what runtime dependencies this has.
One of our deployment configurations is JBoss messaging "standalone", which is basically just the Microcontainer running the JBM POJOs. We would like a management capability in there too, but would want to keep the run time dependencies and footprint to a minumu - otherwise we just end becoming JBoss AS.
You mention remoting - this implies to me that you're not a web UI.
Also I'm guessing a web server, and seam - anything else.
Or maybe I am confusing the whole issue and confusing two different management solutions...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130562#4130562
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130562