Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for Java Environments 4.1.

Configuring JMX and IBM Health Center

Java address spaces need to communicate with the MainView 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.

Note

You can also configure multiple JVMs by using the Configuration Assistant. For more information, see Setting-up-JVM-targets-by-using-the-Configuration-Assistant.

To configure JMX for a JVM

Note

JMX data for IBM z/OS Connect EE and WebSphere Liberty servers is gathered via the Representational State Transfer (REST) local interface. For more information about configuring JMX data collection on these servers, see Enabling-features-in-the-server-xml-file.

Use one of the following procedures:

  • To configure JVMs in the JVM startup command

    Click here to expand...

    1. 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 only WAS (WebSphere Application Server) JVMs)
      -Dcom.sun.management.jmxremote
      -Dcom.sun.management.jmxremote.port=<nnnn>
      -Dcom.sun.management.jmxremote.authenticate=false
      -Dcom.sun.management.jmxremote.ssl=false
      -Djava.rmi.server.hostname=<hostName>

      Note

      You must define a unique port number for each JVM that you want to monitor.

  • To configure JVMs using your JMX configuration file 

    Click here to expand...

    1. 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 ).

    2. In your configuration file, specify the following Java properties:

      javax.management.builder.initial= (specify this property for only WAS (WebSphere Application Server) JVMs)
      com.sun.management.jmxremote
      com.sun.management.jmxremote.port=<nnnn>
      com.sun.management.jmxremote.authenticate=false
      com.sun.management.jmxremote.ssl=false
      java.rmi.server.hostname=<hostName>

      Note

      You must define a unique port number for each JVM that you want to monitor.


    Tip

    For more information about setting up JMX configuration parameters for different JVM types, see the Knowledge Article 000102079. 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.

    Note

    To enable collection of CPU consumption data on IBM CICS JVMs, ensure that the following JVM startup option is defined:

    -XX:+EnableCPUMonitor 

    For more information, see the IBM documentation on configuring CICS.

To configure the Health Center in the JVM startup command

Note

If you are configuring Health Center on a z/OSMF JVM, see Configuring-Health-Center-on-z-OSMF-JVMs.

  1. 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

    Notes

    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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*