Activate controls to drive NTH collection
TIP
To ensure that Near Term History, NTH, is collecting data properly, some specific subsystem and/or agent configuration changes may be necessary. These should be set up via the E3270UI or TEP user interfaces.
The following changes are required for some of the JVM attribute tables.
Any JVM that needs to be monitored must be configured with the OMEGAMON Java Agent and -agentpath. Documentation for this task can be found in IBM Z OMEGAMON for JVMopen in new window
z/OS Connect Servers need an OSGI interceptor and log streams to be defined in order to get API provider and requester data. The steps can be found at IBM Z OMEGAMON for JVMopen in new window
Liberty servers must have the monitoring "MBean" defined in the server’s server.xml file. The steps can be found at IBM Z OMEGAMON for JVMopen in new window