IBM Z® OMEGAMON Data Provider: a part of IBM Z OMEGAMON Integration Monitor

What's new in OMEGAMON Data Provider
A summary of significant changes.
Earlier editions of this documentation
Earlier editions of this documentation are available in PDF only.
Upgrading to the latest APAR level
Some APARs involve performing upgrade steps in addition to the steps described in the corresponding APAR text.
Introduction to OMEGAMON Data Provider
OMEGAMON® Data Provider makes data from z/OS® available to various destinations. Typically, the data consists of metrics or events from z/OS subsystems or applications, and the destinations are analytics platforms that analyze that data.
Installing OMEGAMON Data Provider
If you have the prerequisite software, then OMEGAMON Data Provider is already installed in your z/OS SMP/E target libraries. You need to know the location of those libraries. Also, before configuring OMEGAMON Data Provider, you might need to install some components in other locations.
Getting started with OMEGAMON Data Provider
After installing OMEGAMON Data Provider, you need to configure and then start its components.
Where and how to run OMEGAMON Data Connect
OMEGAMON Data Connect is a Java™ application. You can run OMEGAMON Data Connect anywhere that you can run Java 17 or later, 64-bit edition.
Modifying running components of OMEGAMON Data Provider
To control components of OMEGAMON Data Provider that are running on z/OS , you can use MVS™ system commands, such as MODIFY, STOP, and START.
Adding more OMEGAMON collections to OMEGAMON Data Provider
If you have already configured an OMEGAMON runtime environment to send collections to OMEGAMON Data Provider, then follow the steps here to add more.
Configuration
OMEGAMON Data Provider involves four configuration points: the data source, the two components of OMEGAMON Data Provider (OMEGAMON Data Broker and OMEGAMON Data Connect), and the destination.
Characteristics of output from OMEGAMON monitoring agents
The general characteristics of output from OMEGAMON Data Provider depend on the OMEGAMON Data Connect configuration, and are independent of the data source. However, some specific characteristics depend on the data source.
Troubleshooting
Follow these steps to diagnose and correct problems that you experience with OMEGAMON Data Provider. For example, expected data not arriving at a destination analytics platform.
Messages
Each component involved in OMEGAMON Data Provider writes messages that describe activity or errors.

Related information

Downloadable PDF Documentation