What's new in IBM OMEGAMON for JVM on z/OS V5.4.0
IBM® OMEGAMON® for JVM on z/OS® (OMEGAMON for JVM) V5.4.0 is now a stand-alone product, so it does not require a license for IBM Tivoli® OMEGAMON XE on z/OS. OMEGAMON for JVM supersedes OMEGAMON Monitoring Feature for JVM on z/OS V5.3.0, which is deprecated.
The following features and functions are introduced in OMEGAMON for JVM V5.4.0:
- Address Space Memory and Native Memory workspaces
- New Native Memory analysis continuously monitors JVM native memory category usage, Language Environment® heap, and z/OS address space memory to proactively detect impending out-of-memory conditions. For more information, see Address Space Memory workspace and Native Memory workspace.
- Java™ Health Center Agent
- IBM Java Health Center Agent is packaged with OMEGAMON for JVM. OMEGAMON for JVM provides the latest compatible Health Center Agent, eliminating the requirement to download and deploy the Health Center Agent separately, which improves ease of installation and time to value. The GBL_USS_TKANJAR_PATH parameter is required when OMEGAMON for JVM (KJJ) Agent is configured. This parameter is crucial to PARMGEN’s tailored USS jobs to expand the Health Center Agent .pax files. For more information about the parameter, see PARMGEN PTF UA82508 for APAR OA50912 (4Q16 Interim Feature). For information about the upgrade considerations and the SMP/E maintenance considerations to add the parameter, see Basic upgrade requirements and SMP/E maintenance and upgrade scenarios.
- JVM monitoring enhancements
- OMEGAMON for JVM monitors Java applications that are running APF authorized.
- New monitored attributes
- OMEGAMON for JVM provides situations that support the new monitored attributes. For more information, see Attributes.
- In addition to the JVM subsystem, OMEGAMON for JVM
exposes additional values about the application that is running in the JVM such as name, type, and
instance. You can customize these values to fit your in-house standards. The following table lists
the subsystems and application types that are automatically identified:
Table 1. Subsystems and application types that are automatically identified Subsystems Subsystem types Application types Batch, Unix System Services command-line Standalone N/A CICS Transaction Server CICS JCICS, WebSphere® Liberty, z/OS Connect CICS Transaction Gateway CICSTG CICS TG Applid (system property: product.applid) IBM DB2 DB2 N/A IBM Operational Decision Manager (ODM) ODM ODM server ID (system property: hbr.ssid) IMS IMS Region type: JBP or JMP (system property: com.ibm.ims.regiontype) WebSphere Application Server WebSphere Server instance name WebSphere Liberty Liberty Standalone and z/OS Connect z/OS Management Facility (z/OSMF) z/OSMF N/A
- OMEGAMON XE shared documentation
- The auto-discovery function of z/OS Discovery Library Adapter (DLA) is integrated in the PARMGEN configuration method to simplify the configuration process. During the configuration phase of the OMEGAMON for JVM deployment, you can run the PARMGEN z/OS DLA jobs to automatically discover and fill in the values of some product parameters before you start to edit the configuration profiles. For more information about running the PARMGEN z/OS DLA jobs, see Preparing the configuration profiles by running the KCIJPDLn jobs.
- Support for customized application names
- The com.ibm.omegamon.kjj.appl system property can be used to override the auto-discovered application type for all jobs, regardless of the subsystem type or application type. To override the auto-discovered application type, add Dcom.ibm.omegamon.kjj.appl=custom_application_name to the file that other system properties for the monitored JVM reside in.
- Thread Statistics workspace
- Thread CPU time and CPU utilization are included in Thread analysis, which helps identify loops in Java applications. For more information, see Thread Statistics workspace.
- z/OS Connect workspaces
- The monitoring of z/OS Connect service response time shows real-time and historical service response time. The detailed data for the worst performing requests is also available. For more information, see z/OS Connect Request Details workspace, z/OS Connect Request Summary workspace, and z/OS Connect Slowest Requests workspace.