[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2 Management Interfaces

anonymous wrote : The user is not going to be starting up any other RHQ serves just so they can see the JBM interface, that would suck. Agreed. RHQ is for production management. If you want a small, simple management UI (for, say, developers to use), RHQ is not what you want to use. But, what you will want to do is make your management interface remotely accessible so you CAN plug into a production management environment (like RHQ) so I can manage your jbm services along side of my other production apps/services. So, I can import my jbm services into RHQ's inventory along with my JBossAS servers, and other managed products so, when I *do* deploy jbm in production, I can manage it with all my other things in a single management platform. Because if I have to load up your management console UI separately from my other management tools just to manage jbm, that would suck too. Its a "production" enviroment vs. "development" environment thing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130823#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...