Basic OMEGAMON Data Broker configuration examples
Basic OMEGAMON® Data Broker configurations consist of one store, one forwarder, and one sink (one instance of OMEGAMON Data Connect).
Example: Forwarding without TLS
The following example configures OMEGAMON Data Broker to forward
data to OMEGAMON Data Connect on the same z/OS® instance as OMEGAMON Data Broker
(localhost
) and listening on port 15351:
ZWES.PLUGIN.KAY.ZISDYNAMIC=KAYSISDL
ZWES.PLUGIN.KAY.CIDB=KAYB0001
* Store
KAY.CIDB.STORE.STORE1.NAME=OMEGAMON
* Forwarder and sink
KAY.CIDB.FWD=ON
KAY.CIDB.FWD.FWD1.SOURCE_STORE=OMEGAMON
KAY.CIDB.FWD.FWD1.SINK_HOST=localhost
KAY.CIDB.FWD.FWD1.SINK_PORT=15351
A similar set of OMEGAMON Data Broker configuration parameters is supplied in the sample member TKANSAM(KAYSIP00).
The following example shows the same configuration, but using reusable sink parameters instead of forwarder-scope sink parameters:
ZWES.PLUGIN.KAY.ZISDYNAMIC=KAYSISDL
ZWES.PLUGIN.KAY.CIDB=KAYB0001
* Store
KAY.CIDB.STORE.STORE1.NAME=OMEGAMON
* Sink
KAY.CIDB.SINK.SINK1.HOST=localhost
KAY.CIDB.SINK.SINK1.PORT=15351
* Forwarder
KAY.CIDB.FWD=ON
KAY.CIDB.FWD.FWD1.SOURCE_STORE=OMEGAMON
KAY.CIDB.FWD.FWD1.SINK=SINK1
Reusable sink parameters are especially useful in advanced configurations where multiple forwarders use the same sink. However, even in a basic configuration, you can choose to use reusable sink parameters to separate the different types of parameters.
Example: Forwarding with TLS using a RACF key ring
ZWES.PLUGIN.KAY.ZISDYNAMIC=KAYSISDL
ZWES.PLUGIN.KAY.CIDB=KAYB0001
* Store
KAY.CIDB.STORE.STORE1.NAME=OMEGAMON
* Forwarder and sink
KAY.CIDB.FWD=ON
KAY.CIDB.FWD.FWD1.SOURCE_STORE=OMEGAMON
KAY.CIDB.FWD.FWD1.SINK_HOST=localhost
KAY.CIDB.FWD.FWD1.SINK_PORT=15351
KAY.CIDB.FWD.FWD1.SECURITY=TLSv1.2
KAY.CIDB.FWD.FWD1.FIPS=ON
KAY.CIDB.FWD.FWD1.KEYRING=KAYSIS01/KAYring
This example is based on the following assumptions:
- You have configured the TCP input of OMEGAMON Data Connect to use TLSv1.2.
- At least one of the FIPS cipher suites specified here by OMEGAMON Data Broker matches a cipher suite specified by OMEGAMON Data Connect.
- You have created a RACF® key ring named
KAYring
, owned by userKAYSIS01
(the user that runs the Zowe™ cross-memory server instance that hosts the OMEGAMON Data Broker plug-in). - The key ring contains a certificate that OMEGAMON Data Broker (the client) can use to authenticate OMEGAMON Data Connect (the server).
- OMEGAMON Data Connect does not require client authentication.
If OMEGAMON Data Connect requires client authentication, add the following parameter:
KAY.CIDB.FWD.FWD1.CERTLABEL=OMDPcert
where OMDPcert
is the
label (alias) of the client certificate in the key ring.
Here is the same configuration with reusable sink parameters:
ZWES.PLUGIN.KAY.ZISDYNAMIC=KAYSISDL
ZWES.PLUGIN.KAY.CIDB=KAYB0001
* Store
KAY.CIDB.STORE.STORE1.NAME=OMEGAMON
* Sink
KAY.CIDB.SINK.SINK1.HOST=localhost
KAY.CIDB.SINK.SINK1.PORT=15351
KAY.CIDB.SINK.SINK1.SECURITY=TLSv1.2
KAY.CIDB.SINK.SINK1.FIPS=ON
KAY.CIDB.SINK.SINK1.KEYRING=KAYSIS01/KAYring
KAY.CIDB.SINK.SINK1.CERTLABEL=OMDPcert
* Forwarder
KAY.CIDB.FWD=ON
KAY.CIDB.FWD.FWD1.SOURCE_STORE=OMEGAMON
KAY.CIDB.FWD.FWD1.SINK=SINK1