Java address spaces need to communicate with the BMC AMI Ops Monitor for Java Environments PAS to collect JMX data and Health Center data.
In order to collect JMX data and Health Center data for a JVM, you need to configure the JVM by adding Java properties to the JVM profile.
Use the following procedures to configure JMX and the Health Center for each target JVM that you want to monitor.
Use one of the following procedures:
Important
This procedure is not applicable if you are using IBM WebSphere Application Server Liberty (Liberty servers).
To configure JVMs in the JVM startup command
Click here to expand...
In the JVM profile, specify the following Java properties for each JVM that you want JMX to monitor:
-Djavax.management.builder.initial= (Specify this property for WAS (WebSphere Application Server) JVMs only. Ensure that there is a space after the equals (=) sign)
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=<nnnn> (Specify any port number that is not currently used. The port number can be greater than 1024, or zero.)
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Djava.rmi.server.hostname=<hostName>
Important
You must define a unique port number for each JVM you want to monitor.
To configure JVMs using your JMX configuration file
Click here to expand...
In the JVM startup command, specify the following string:
-Dcom.sun.management.config.file=<filePath>
Replace filePath with the location of your JMX configuration file (such as /MyDirectory/MyJmxConfigFile ).
In your configuration file, specify the following Java properties:
javax.management.builder.initial= (Specify this property for WAS (WebSphere Application Server) JVMs only. Ensure that there is a space after the equals (=) sign)
com.sun.management.jmxremote
com.sun.management.jmxremote.port=<nnnn> (Specify any port number that is not currently used. The port number can be greater than 1024, or zero.)
com.sun.management.jmxremote.authenticate=false
com.sun.management.jmxremote.ssl=false
java.rmi.server.hostname=<hostName>
Important
You must define a unique port number for each JVM that you want to monitor.
Tip
View the following Knowledge articles for additional information:
For more information about setting up JMX configuration parameters for different JVM types, see the Knowledge Article 000205011.
For more information about REST security errors, see Knowledge Article 000389575.
You can access the Knowledge Base directly at http://www.bmc.com/available/search-kb.html or from the BMC Support Central website (http://www.bmc.com/support). In addition, you can refer to the documentation from your JVM application.
Important
To enable collection of CPU consumption data on IBM CICS JVMs, ensure that the following JVM startup option is defined:
For more information, see the IBM documentation on configuring CICS.
In the JVM profile, specify the following Health Center properties for each JVM that you want to monitor:
-Xhealthcenter:level=off,port=<nnnnn>,transport=jrmp
-Dcom.ibm.diagnostics.healthcenter.data.profiling=off
Important
Consider the following information:
- Specifying the port is optional. The Health Center agent will start looking for an available port from port 1972 (or the specified port) for 100 ports.
- Setting level=off specifies that the agent can start collecting Health Center information only when the MJE JVM connects. Alternatively, to collect as many loaded classes as possible, start the agent with level=full. You might want to set level=full if setting level=off does not provide the required loaded classes.