Watch this short, 2 minute demo: https://network.jboss.com/confluence/display/JON2/Demo-Intro All the features you see in this core UI comes out of box from RHQ - you write a plugin that sits in our agent, and you get all of these features without having to write any UI or server-side code. You just write code that talks to the new remoting management interface and RHQ takes care of the rest. So, for example, if you want to support the ability for your customers to remotely view and edit configuration for your remoting services, you have your plugin implement the Configuration facet: http://svn.rhq-project.org/repos/rhq/trunk/modules/core/plugin-api/src/ma... Your configuration facet implementation would talk to your remoting services management interface to set configuration properties directly on your remoting objects. If you want to monitor your remoting services, you implement the MeasurementFacet: http://svn.rhq-project.org/repos/rhq/trunk/modules/core/plugin-api/src/ma... The measurement facet implementation talks to your remoting services management interface to obtain measurements emitted by them. Take a look at our other facets: http://svn.rhq-project.org/repos/rhq/trunk/modules/core/plugin-api/src/ma... to see what management features are supported. You can implement one, some or all of the facets. If you do not implement one, RHQ simply ignores that functionality for your plugin and assumes it is not supported (so if you do not implement the Configuration facet, the core UI will not show you the config screens that would have allowed you to remotely configure your remoting services). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130757#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...