Configuring Health Center on z/OSMF JVMs

To configure Health Center on z/OSMF JVMs, you need to override the values specified in the JVM profile (jvm.options) and the server.xml file.

  1. Create the following files in the z/OSMF configuration directory:
    • local_override.cfg, which overrides the Health Center properties specified in the jvm.options file
    • server_override.xml, which overrides the features specified in the server.xml file

  2. In the local_override.cfg file, specify the following line: 

    -Xhealthcenter:level:off,transport:jrmp,port=<nnnn>

Related topics

Configuring-JMX-and-IBM-Health-Center

Enabling-features-in-the-server-xml-file

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

    z/OSMF merges the local_override.cfg file into the jvm.options file.

  2. In the server_override.xml file, specify the following features:

    <server>

     <featureManager>
     <feature>monitor-1.0</feature>
     <feature>restConnector-2.0</feature>
     </featureManager>

    </server>

    z/OSMF processes the server_override.xml file in addition to the server.xml file.

    Important

    The monitor-1.0 feature is optional. If the z/OSMF user ID is the same as the server ID, you can include this feature for more efficient processing.

 

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