Configuring the Federator to mirror data on a database

Starting from the Dynamic Workload Console V10.2.3, the Federator component is automatically installed with the console to mirror (replicate) the events related to the z/OS current plan on a configured database. For this function, it is required that you are using IBM Z Workload Scheduler v10.2, or later.

Data mirroring enables you to:

Monitor your objects from the Orchestration Monitor page of the Dynamic Workload Console (for details, see Orchestration Monitor overview).
Starting from DWC 10.2.4, you can also run OQL queries (for details, see Using Orchestration Query Language).
Perform actions on the monitored objects through the REST APIs V2, with which you can also run OQL queries. (For details, see Using Orchestration Query Language.)

To configure the Federator, perform the following steps:

According to your operating system, browse to the fed_variables.xml file, which is created at installation time in the following folder:

On Windows

<DWC_home>\usr\servers\dwcServer\configDropins\templates\zconnectors

On UNIX and z/OS

<DWC_home>/usr/servers/dwcServer/configDropins/templates/zconnectors
Edit the file by setting the following variables:
federator.secret

The secret key string used to register the z/OS engine to the Federator, in the format UTF-8. Ensure that you use a character set that is compatible with the CODEPAGE parameter specified in the OPCOPTS initialization statement.
This variable is case-sensitive. You can specify up to 36 alphanumeric characters. Special characters, except blanks and single quotation marks, are allowed.

mirroring.cleanup.interval
Number of days after which the following records are deleted from the database:
- Records flagged as archived
- Records not updated over that time range which are no longer in the current plan.
The default is 0, meaning that the database stores only the records that are present in the current plan.
uno.federator.engine.jwt.expiration.duration

The interval of time after which the authentication token expires, set in the ISO 8601 format. For example, to specify an interval of 50 days, set P50D. To specify an interval of 45 hours, set PT45H. The default is 30 days.
According to your operating system, browse to the jwtsso.xml file, which is created at installation time in the following folder:

On Windows

<DWC_home>\usr\servers\dwcServer\configDropins\templates

On UNIX and z/OS

<DWC_home>/usr/servers/dwcServer/configDropins/templates
Copy the jwtsso.xml file to the following path:

On Windows

<DATA_dir>\usr\servers\dwcServer\configDropins\overrides

On UNIX and z/OS

<DATA_dir>/usr/servers/dwcServer/configDropins/overrides
If you are upgrading from any version earlier than 10.2.3, browse to the datasource_db_vendor.xml file, which is created at installation time in the following folder:

On Windows

<DWC_home>\usr\servers\dwcServer\configDropins\templates\datasources

On UNIX and z/OS

<DWC_home>/usr/servers/dwcServer/configDropins/templates/datasources
Locate in the file the section named jndiName="jdbc/feddb".
Copy the section and paste it into the datasource.xml file located in the following path:

On Windows

<DATA_dir>\usr\servers\dwcServer\configDropins\overrides

On UNIX and z/OS

<DATA_dir>/usr/servers/dwcServer/configDropins/overrides
Stop and restart the Dynamic Workload Console server.