HP OSMS white paper: How to Monitor JBoss v4.0.3 SP1 with HP SIM using SNMP

to the wrapper class implementation as the key to be mapped to a corresponding value. A default

implementation of this interface comes with the class,

org.jboss.jmx.adaptor.snmp.agent.NotificationWrapperSupport. This implementation

recognizes the following set of tags:

Table 1 Wrapper Class Tags and Descriptions

DescriptionTag

n.getMessage()n:message

n.getSequenceNumber()n:sequenceNumber

n.getSequenceNumber()n:timeStamp

n.getType()n:type

n.toString()n:all

n.getClass().getName()n:class

snmp agent/adaptor start timea:startTime

snmp agent/adaptor up timea:uptime

snmp agent/adaptor trap counta:trapCount

looked-up in n.getUserData() if it's a HashMapany-other-tag

Configuring the JBoss Deployment Descriptor

Once the JBoss service is configured, you must configure the deployment descriptor to deploy the service.

A deployment descriptor is an XML file that describes how an application should be deployed. It directs

JBoss to deploy the service with specific container options and describes specific configuration dependencies

that JBoss must resolve. This is facilitated by the

/usr/local/jboss<version>/server/default/deploy/snmp-adaptor.sar/META-INF/jboss-service.xml

file. The following example of this file includes additional comments to describe its use:

<?xml version="1.0" encoding="UTF-8"?>

<!--

$Id: OSMS_WP_Mon_Jboss_SNMP.xml,v 1.21 2006/09/13 18:09:55 loval Exp $

The snmp adaptor will not only subscribe for notifications

upon starting, but will also monitor for new MBeans created within the

JMX agent and subscribe to them dynamically as they come and go,

as long as the the mbean subscription information matches their names.

Have a look at the provided example configuration files for more info.

SnmpAgentService produces by default a "coldstart" notification when started.

In addition, by setting the HeartBeatPeriod attribute to a value greater

than zero, the adaptor configures a Timer MBean to produce heartbeat

notifications at regular intervals (measured in seconds).

The adaptor itself uses JoeSNMP by OpenNMS for its SNMP engine. The

trap generation mechanism can be changed or extended with custom classes

able to extract information from notifications subsclasses unknown

to the NotificationWrapperSupport class provided with the adaptor.

For more information on using or extending this mechanism, please

consult the jboss documentation or the source code.

TrapdService is a simple MBean that acts as an SNMP Manager. It

listens to a configurable port for incoming traps and logs them

as DEBUG messages using the system logger. You can modify the log4j