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

-->

<address>localhost</address>

<local-address></local-address>

<local-port></local-port>

</manager>

<local-address></local-address>

<local-port></local-port>

</manager>

</manager-list>

The notifications.xml configuration file is used to specify how the intercepted JMX notifications, to

which the snmp-adaptor subscribes, will be mapped to SNMP traps. This mapping is driven by matching

the notification type of the JMX notification to an SNMP trap, as shown in this notifications.xml file:

<?xml version="1.0"?>

<!--

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

This configuration file controls the mapping of JMX notification

onto SNMP traps. The key for the mapping is considered to be the

notification type. The mapping concerns:

1. Generic trap id

2. Specific trap id

3. Enterprise OID

4. The trap payload comprised of notification variables

mapped to specific OIDs.

Notification extractor classes may be used to extract info from

arbitrary notification subclasses.

This is the most complex part of the SNMP adaptor configuration.

For more information on using or extending this mechanism,

please consult the jboss documentation or the source code.

-->

<notification-map-list>

<notification-type>jboss.snmp.agent.heartbeat</notification-type>

<var-bind-list wrapper-class="org.jboss.jmx.adaptor.snmp.agent.NotificationWrapperSupport">

<var-bind>

<tag>a:uptime</tag>

</var-bind>

<var-bind>

<tag>a:trapCount</tag>

</var-bind>