Configuring OMEGAMON Data Broker

OMEGAMON® Data Broker is a plug-in for the Zowe™ cross-memory server. You can configure OMEGAMON Data Broker using either the server that is supplied with OMEGAMON Data Provider (the best and easiest choice for most users) or a server in an existing separate Zowe installation.

Before you begin

If you do not have an existing separate Zowe installation, skip to Configuring OMEGAMON Data Broker using the server supplied with OMEGAMON Data Provider.

Otherwise, decide whether to use the server that is supplied with OMEGAMON Data Provider or a server in a separate Zowe installation. The following tables describe advantages and disadvantages of each option.

Tip: Using the server supplied with OMEGAMON Data Provider is the best and easiest choice for most users. Using an existing server in a separate Zowe installation introduces compatibility, configuration, and maintenance issues. If you're content to accept this tip without reading more, skip to Configuring OMEGAMON Data Broker using the server supplied with OMEGAMON Data Provider.
Table 1. Advantages of using the server supplied with OMEGAMON Data Provider
Advantages of using the server supplied with OMEGAMON Data Provider Corresponding disadvantages of using an existing server in a separate Zowe installation
You don't need to install Zowe. Instead, OMEGAMON Data Provider supplies the few Zowe parts required to run OMEGAMON Data Broker. Installing Zowe involves more effort than using the parts that are supplied with OMEGAMON Data Provider. A Zowe installation involves many parts that OMEGAMON Data Provider does not use.
Guaranteed compatibility between the server and OMEGAMON Data Broker. Compatibility issues:
  • You must check that the Zowe version is compatible with OMEGAMON Data Broker: currently, Zowe 2.12.0 or any later 2.x.x.
  • You must reconsider compatibility whenever you update either OMEGAMON Data Provider or your separate Zowe installation.
OMEGAMON Data Provider supplies the load modules for the server and OMEGAMON Data Broker in a single library, TKANMODP. The STEPLIB for the server JCL can refer to that single library, without relocating any members. Configuration issue:
  • You must decide how to make OMEGAMON Data Broker available to the server; how to include the required load modules in the STEPLIB for the server JCL.

Maintenance issue:

  • You must manage how to apply updates to the OMEGAMON Data Broker load modules.
Using a dedicated server for OMEGAMON Data Broker enables you to manage the configuration, maintenance, and availability of OMEGAMON Data Provider independently of a separate Zowe installation.
Tip: You can run multiple instances of the Zowe cross-memory server on the same z/OS® instance. A dedicated server for OMEGAMON Data Broker can coexist on the same z/OS instance with a server in a separate Zowe installation.
 Maintenance issue:
  • You must manage the effects of updates to the Zowe installation on OMEGAMON Data Broker.
Table 2. Advantages of using an existing server in a separate Zowe installation
Advantages of using an existing server in a separate Zowe installation Corresponding disadvantages of using the server supplied with OMEGAMON Data Provider
Minimizes the number of address spaces on z/OS.

For example, if you are already running compatible Zowe cross-memory servers in the z/OS instances where you need to run OMEGAMON Data Broker, and you are comfortable managing the compatibility, configuration, and maintenance issues, then you can host OMEGAMON Data Broker in those existing servers rather than using dedicated servers for OMEGAMON Data Broker.

 Requires a new address space.
Uses existing PROCLIB and PARMLIB (JCL procedure and configuration) members. Requires you to create a JCL procedure, a configuration member, and a corresponding started task.

If you need more information to help you decide which option to choose, review the corresponding configuration procedures for each option.

Procedure

Follow the procedure for configuring OMEGAMON Data Broker using your chosen option.