Upgrading a JVM to OMEGAMON AI for JVM, 6.1.0

IBM® Z OMEGAMON® AI for JVM supports upgrading a JVM from versions 5.4.0 and 5.5.0 to 6.1.0.

If you have installed OMEGAMON AI for JVM, 6.1.0 using the same RTE USS directory as a previous version of OMEGAMON for JVM (version 5.4.0 or 5.5.0), the Configuration Manager GENERATE job will replace the existing files from the previous release. In most cases you will only need to restart the JVM to start using the latest features and benefits of version 6.1.0.

If you are upgrading a JVM from version 5.4.0 or a JVM configured with version 5.5.0 using the IBM Java Health Center agent, you will need to perform an additional step after running the Configuration Manager GENERATE job. The Health Center is no longer used as a source of monitoring data in OMEGAMON AI for JVM, 6.1.0, and it will not function unless the Java options are changed. First, refer to the relevant section of Configuring Java Applications for Monitoring for the application that you want to monitor to find where to specify the JVM startup options for the application. Find and remove references to Health Center agents such as:

-Xhealthcenter:level=inprocess,disableCH

-Xbootclasspath/a:/RTE_USS_RTEDIR/RTE_NAME/kan/hca_64/lib/ext/healthcenter.jar

-agentpath:/RTE_USS_RTEDIR/RTE_NAME/kan/hca_64/bin/
 libhealthcenter.so=
 path=/RTE_USS_RTEDIR/RTE_NAME/kan/hca_64,
 level=inprocess,disableCH

The minimal JVM options now required are:

-javaagent:/RTE_USS_DIR/RTE_NAME/kan/bin/IBM/kjj.jar
-Xbootclasspath/a:/RTE_USS_DIR/RTE_NAME/kan/bin/IBM/kjjboot.jar
-agentpath:/RTE_USS_DIR/RTE_NAME/kan/bin/IBM/libkjjagent_64.so

Or, for 31-bit JVM
-agentpath:/RTE_USS_DIR/RTE_NAME/kan/bin/IBM/libkjjagent.so

If you were monitoring z/OS Connect using a previous version of OMEGAMON for JVM, then you should also examine server.xml configuration for the server. The previous generation interceptors have been deprecated. Any references to feature omegamon:omegamonRequestMonitor or omegamon:omegamonRequestMonitor-2 should be changed to use the third generation feature omegamon-3:omegamonRequestMonitor-3. Follow the instructions in Configuring z/OS Connect for API monitoring.

You can safely delete the files:

  • com.ibm.omegamon.kjj.interceptor_2.0.jar
  • com.ibm.omegamon.kjj.interceptor_2.0.mf