From jbm's point of view, you just expose your management
"stuff" via JMX MBeans. If you want jbm to be managed "by something"
(RHQ or something else) you need to do this no matter what. Since jbm is written in Java,
JMX seems to be the logical choice. jbm is as lightweight as you make it - the jbm MBeans
are hosted by jbm somewhere (maybe it has its own MBeanServer, maybe it uses the JRE5
platform MBean Server, maybe its running in JBossAS and it uses JBoss's MBeanServer...
its up to you).
Then, you can either:
a) write your own client that connects to the MBeanServer that exposes your MBeans, and
write your own management application/UI that makes JMX API calls to interact with the jbm
management facilities.
or
b) write an RHQ plugin that connects to the MBeanServer that exposes your MBeans (no Java
code needed on your part if the JMX plugin can do everything you need) and utilize the RHQ
feature set that the RHQ Server core UI provides.
and I do not have an uncle named Bob ;)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130801#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...