Skip to Content

BMC AMI Ops Monitor for Java Environments product overview and architecture

BMC AMI Ops Monitor for Java Environments provides comprehensive observability for Java Virtual Machines (JVMs) running within the z/OS address space. By leveraging automated discovery and deep integration with the z/OS System Management Facilities (SMF) and JVM tool interfaces, it provides the data required to manage complex middleware stacks such as z/OS Connect EE, WebSphere Application Server (WAS), and Liberty Profile.

  • Memory management: Continuous tracking of heap and non-heap memory allocation, featuring real-time telemetry of garbage collection (GC) frequency, cycle duration, and post-collection occupancy levels to identify and mitigate non-deterministic JVM pause-time overhead and application latency spikes
  • Central processor (CP) and zIIP dispatching: Granular reporting on CPU runtime, specifically isolating zIIP-eligible versus zIIP-on-CP spillover to optimize workload placement and minimize General Purpose (GP) processor MSUs
  • Thread and lock contention: Identification of thread-level bottlenecks, synchronization delays, and deadlocks within the JVM that impact transaction throughput
  • API observability: Full lifecycle monitoring of RESTful request headers and payloads within z/OS Connect EE, providing end-to-end tracing from the API gateway to backend CICS or Db2 subsystems

This BMC Experience Guide is designed to help you follow best practices when implementing and managing the BMC AMI Ops Monitor for Java Environments product. It provides a detailed walkthrough of essential tasks, including generating Java heap dumps, redirecting those dumps to alternate locations, and configuring and managing USS home directories to support Java heap dump capture.

Warning

Important

To log CPU and SMF data, the architecture also includes the BMC Next Generation Logger (NGL) component. NGL runs on a BMC Execution Component for z/OS (DBC) subsystem. The BMC Execution Component for z/OS was previously named Db2 Component Services.

BMC AMI Ops Monitor for Java Environments architecture

The following figure shows the process for Health Center requests. The figure does not include the process for JMX.

1773996919420-750.png

 

 

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

Best practices for implementing and managing BMC AMI Ops Monitor for Java Environments