From OpenNMS

The default configuration is for the monitoring to be done with RMI, but if your servers are behind a firewall then you can use the HTTP option. To do this, edit the capsd-configuration.xml, poller-configuration.xml, and collect-configuration files to change the factory property to “HTTP” and modify the invoker-suffix property. More details are contained in those files. You also need to open port 4444 in your firewall.

The jmx-datacollection-config.xml file contains a list of MBeans that are monitored. Due to the large number that are available in JBoss, only the service type MBeans are listed. In the file you will see two types of MBean notations used. The normal object name, and an object name with a ‘,*’ in it. This type permits the querying of object names and then the querying for their attributes. The goal was to support the ability to easily monitor a many MBeans and attributes. For now, I’d suggest not using this approach since there are some significant downsides.

This version works for both JBoss 3.2 and 4.0, although the default is 4.0.

Although this is the JMX version we still use a few of the snmp files. If you want to change the formatting of the pre-defined graphs then look at the bottom of the snmp-graph.properties file in the JBoss section. No thresholds have been set, you’ll need to determine what those should be. All the RRD files exist in the <rrd dir>/snmp/<node id>/jboss directory.

Any feedback, ideas on how to make it easier to configure and use would be greatly appreciated.