We struggled to find information on making this template work. Finally we landed on 2 simple configuration changes.
1. For each server we want to monitor, two configurations
Configure the /opt/IBM/WebSphere/AppServer/java/jre/lib/management/management.properties
Snippet:
# ################ RMI Access file location #####################
#
# com.sun.management.jmxremote.access.file=filepath
# Specifies location for access file
# This is optional - default location is
# $JRE/lib/management/jmxremote.access
#
# If the property "com.sun.management.jmxremote.authenticate" is set to
# false, then this property and the password & access files are ignored.
# Otherwise, the access file must exist and be in the valid format.
# If the access file is empty or non-existent then no access is allowed.
#
# For a non-default password file location use the following line
# com.sun.management.jmxremote.access.file=filepath
#Below to enable remote JMX queries in Orion
com.sun.management.jmxremote.port=9001
com.sun.management.jmxremote.ssl=false
com.sun.management.jmxremote.authenticate=false
2. On the Websphere server go to the server detail, Server Infrastructure/Java and Process Management -> Process definition > Java Virtual Machine
Add “-Djavax.management.builder.initial= -Dcom.sun.management.jmxremote” to “Generic JVM arguments
