No special configuration is necessary if monitoring will take place locally. However, JMX must be enabled for remote monitoring. This is done by adding a few settings to the server vmoptions file. The relevant
.vmoptions file is located in the root of the server installation folder of a single server, or the root of the installation folder of the master server in the case of a node setup (Hereafter this folder will be referred to as
Add the following to the
-Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false
- Add the following to the .vmoptions file, instead of the lines provided in the section above.
-Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.ssl=true -Dcom.sun.management.jmxremote.authenticate=true -Dcom.sun.management.jmxremote.password.file=../conf/jmxremote.password -Dcom.sun.management.jmxremote.access.file=../conf/jmxremote.access
- Create the access authorization file
CLC_SERVER_BASE/conf/jmxremote.accessand write the following in it:
monitorRole readonly controlRole readwrite
- Create the password file
CLC_SERVER_BASE/conf/jmxremote.passwordand write the following in it:
monitorRole clcserver controlRole clcserver
Further information about setting up JMX monitoring can be found in the Oracle guide on Monitoring and Management Using JMX Technology http://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html.