View Source

As the monitoring tools can use SNMP probes to get information from the JVM running Petals ESB, we need to enable the SNMP agent of the JVM of each Petals ESB node. On each Petals node, in the [environment configuration|Container Configuration#EnvironmentConfig] file, uncomment the system properties relative to the SNMP agent:
{code}
# Uncomment following lines to enable SNMP agent of the JVM
PETALS_JAVA_OPTS="$PETALS_JAVA_OPTS -Dcom.sun.management.snmp.port=16161"
PETALS_JAVA_OPTS="$PETALS_JAVA_OPTS -Dcom.sun.management.snmp.interface=0.0.0.0"
PETALS_JAVA_OPTS="$PETALS_JAVA_OPTS -Dcom.sun.management.snmp.acl.file=/etc/petals-esb/default-snmp.acl"
{code}
Adjust your SNMP port, interface and ACL.
{note}Caution, if Petals ESB runs with a user different from root, you need to use a port upper than 1024. To use a port lower than 1024 with a Petals ESB launches with a standard user, refers to the utility *privbind* (available in standard Ubuntu repository).{note}
{note}To use the same port on the same machine for several java processes, refers to snmpd used as proxy.{note}
{note}Caution, the ACL file should be accessible (read and write: 'chmod 600 xxx') only by the user running the JVM process.{note}
{warning}If you use OpenJDK as Java virtual machine, you can't enable the SNMP agent. It is missing because of a non-free implementation. Move to the JVM provided by Oracle.{warning}
{info}[Get more information on enabling SNMP into a JVM|http://download.oracle.com/javase/1.5.0/docs/guide/management/SNMP.html]{info}{info}[Get more information on the Java Virtual Machine MIB|http://download.oracle.com/javase/1.5.0/docs/guide/management/JVM-MANAGEMENT-MIB.mib]{info}