Publishing OMEGAMON AI for JVM data to analytic platforms for AI Ops (including OMEGAMON Data Provider)

OMEGAMON® Data Provider makes OMEGAMON attributes available to applications and analytics platforms outside of OMEGAMON. Historical collections are a prerequisite for using OMEGAMON Data Provider.

To create historical collections, use the OMEGAMON enhanced 3270 user interface (e3270UI) or Tivoli® Enterprise Portal (TEP). For more information about creating historical collections, see the OMEGAMON documentation for e3270UI and TEP: https://www.ibm.com/docs/en/om-shared?topic=software-optional-configure-historical-data-collection.

All OMEGAMON® AI for JVM monitoring tables are eligible for publishing to OMEGAMON Data Provider. This includes tables that contain static information that do not have corresponding history workspaces, such as environment data like system properties and environment variables.

History collection can be enabled for the following OMEGAMON AI for JVM tables, making them eligible for use with OMEGAMON Data Provider

Table 1. OMEGAMON AI for JVM tables eligible for history collection
Attribute group	Table Name	Available for ODP data streaming
JVM CPU attributes	CPU	Yes
JVM Environment Data attributes	ENVIRON	Yes
JVM Environment Data Details attributes	ENVDET	Yes
JVM Garbage Collection attributes	GCSUMM	Yes
JVM Health Summary attributes	HEALTH	Yes
JVM Native Memory attributes	NATMEM	Yes
JVM Threads attributes	THREADS	Yes
JVM WebSphere Liberty Thread Pools	WLPTHPLM	Yes
JVM WebSphere Liberty Connection Pool Statistics	WLPCNPLS	Yes
JVM WebSphere Liberty Server Information	WLPSRVIN	Yes
JVM WebSphere Liberty Web Application Metrics	WLPWBAM	Yes
JVM WebSphere Liberty Session Statistics	WLPSESM	Yes
JVM Virtual Memory attributes	ZOSMEM	Yes
z/OS Connect API Provider Summary	ZCSUMM	Yes
z/OS Connect API Requester Summary	ZCOUTBSUM	Yes

Adding OMEGAMON AI for JVM to KAYOPEN for OMEGAMON Data Provider

OMEGAMON Data Provider uses RKANPARU library member KAYOPEN to specify destinations for historical collections. The KAYOPEN member is optional. If you omit it, then collected attributes are sent only to the persistent data store (PDS), not OMEGAMON Data Broker. You only need to collect history for the tables that you intend to publish the data to OMEGAMON Data Provider.

The collections section of the KAYOPEN member of RKANPARU should only specify a destination of “open” for tables that do not have history workspaces, as shown in the following excerpt:


- product: kjj
  table: environ
  interval: 0
  destination:
    - open
- product: kjj
  table: envdet
  interval: 0
  destination:
    - open
- product: kjj
  table: threads
  interval: 0
  destination:
    - open

If you do collect history for these tables, but do not include selection criteria in member KAYOPEN of RKANPARU, then the data will be unnecessarily stored in the persistent data store (PDS). Doing so will consume more DASD space than is necessary.

For more information about OMEGAMON Data Provider, see https://www.ibm.com/docs/en/om-im/5.6.0?topic=monitor-introduction.

IBM Z OMEGAMON Data Provider and IBM Z OMEGAMON AI Insights usage is restricted to only processing the data originating from the IBM products and IBM suites that include these products. To use IBM Z OMEGAMON Data Provider and IBM Z OMEGAMON AI Insights you must be licensed for an authorized product (IBM Z OMEGAMON AI for z/OS 6.10, IBM Z OMEGAMON AI for Networks 6.1.0, or IBM Z OMEGAMON AI for JVM 6.1.0) or for a suite (IBM Z Service Management Suite, IBM Z Monitoring Suite, or IBM zSystems Integration for Observability Suite). A single installation of IBM Z OMEGAMON Data Provider can be used for multiple authorized standalone products and for data from all IBM Z OMEGAMON Agents included in the suites.

IBM Z OMEGAMON Data Provider included with the products (IBM Z OMEGAMON AI for z/OS 6.1, IBM Z OMEGAMON AI for Networks 6.1, or IBM Z OMEGAMON AI for JVM) usage is restricted to data being used by IBM Z OMEGAMON AI Insights. For more information about OMEGAMON AI Insights, see https://www.ibm.com/docs/en/zoai/2.1?topic=introduction-overview.

Customers that would like to use IBM Z OMEGAMON Data Provider to send data to additional consumers such as Splunk or IBM Instana can obtain usage entitlement via one of the suites that include IBM Z Integration Monitor, which are: IBM Z Service Management Suite (IZSMS), IBM Z Monitoring Suite (IZMS), or the new IBM zSystems Integration for Observability Suite (IZIO).