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

[bytor99999]

Hi guys, glad to be a part of this conversation.

After reading through the thread, I thought I'd add my 2 cents with regards to using RHQ and Embedded Console, if that is the route you should choose. (Which I think is the best route :) )

OK, so think of this in just three parts.
1) The UI (Embedded Console)
2) Plugins and the RHQ Plugin Container
3) Your Management Interface for JBM

I hope you don't mind be going top down.

1) The Embedded Console is just a Seam app, so all it needs is something that can "deploy" a Seam app, I believe that includes the Microcontainer. The great thing about the console is that it is generic, just create a plugin and drop it in the plugins dir, and the console will display it nice and pretty. It does use the RHQ plugin container embedded in it. Think of this as an embedded RHQ agent, so no seperate server or agent to start up.

So its dependencies are
Seam
JSF
RichFaces
JSTL
JDom
3 apache commons jars
RHQ core

2) Plugins
You include whatever plugins you want the UI to display. This is the only thing for the UI that you will need to create. Mazz gave you all the info about plugins and what they need. 

The plugin's dependencies are anything it needs to communicate to what it plans to manage and monitor. In a lot of cases it might already have been provided for you. In looking at our plugins, it is only the jmx-plugin that has one jar with it for the EMS library that it uses.

3)Your Management Interface for JBM.
Now this is completely up to you. All the plugin will need is an ability to connect to it, locally or remotely. Remotely more for everyone to re-use your plugin in other servers. So you can choose any transport you want. You just might need to include that transports jar files in the plugin jar.


Let me use an example of the AS 5 plugin.

AS 5 has the Profile Service which is the management interface that AS 5 exposes (3). In the AS 5 plugin, it simply does a JNDI lookup for the profile service and then just codes to that api. In the rhq-plugin.xml I define my resources and what props, metric statistics and operations each resource type can expose (2).

I simply drop the AS 5 plugin into the plugins directory of the Embedded Console war and now the Console manages and monitors AS 5 (1).

So the dependencies are very small, the JON team designed and built it such that it was as simple as possible for plugin developers to add management and monitoring capabilities to their products.

I hope that helps.

Thanks

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130901#4130901

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130901