Db2 for z/OS CDC Connector > Introduction to Db2 for z/OS CDC Connector > Integration with the PowerExchange CDC environment
  

Integration with the PowerExchange CDC environment

You must have a functional on-premises PowerExchange CDC environment that can capture change records from Db2 source tables on a z/OS system and log the change records to a remote PowerExchange Logger on Linux, UNIX, and Windows system. The Db2 for z/OS CDC Connector retrieves change records from the PowerExchange Logger for Linux, UNIX, and Windows log files.
You must have a license that allows your organization to use the Db2 for z/OS CDC Connector and PowerExchangeClient packages on a Linux or Windows system. On each system from which you plan to use Db2 for z/OS CDC Connector, install the Secure Agent. After you start the Secure Agent the first time, the Db2 for z/OS CDC Connector and PowerExchangeClient package are installed locally. You then can use Cloud Data Integration, Administrator, and Monitor interfaces to configure Db2 for z/OS CDC connections, mappings, and mapping tasks and to run and monitor mapping tasks.
The following image shows the general architecture of the Db2 for z/OS CDC Connector components in relation to Cloud Data Integration, the remote Db2 for z/OS source system, and the remote PowerExchange Logger for Linux, UNIX, and Windows system:
On-prem PowerExchange components on the z/OS source system and Logger for LUW system in relation to on-prem Db2 for z/OS CDC Connector and IICS components and the IICS cloud. Also shows data flow from the source to target.
This configuration spans the following on-premises systems:
Based on this configuration, the following processing occurs:
  1. 1The PowerExchange capture routine actively captures change records from Db2 transaction logs and sends the records to the PowerExchange Logger for z/OS on a continuous basis.
    2. To capture change records, the PowerExchange capture routine uses the capture registrations that are recorded in the PowerExchange CCT file. You defined a capture registration for each Db2 source table in the PowerExchange Navigator. The PowerExchange Navigator generated a corresponding extraction map, which will be used to extract the change records.
  2. 2Because remote logging is enabled, PowerExchange sends the change records that are in the PowerExchange Logger for z/OS log files to the remote PowerExchange Logger for Linux, UNIX, and Windows.
  3. 3The PowerExchange Logger for Linux, UNIX, and Windows logs the change records in its log files.
    4. The pwxccl.cfg file defines the PowerExchange Logger configuration.
  4. 4When you design a mapping in Data Integration, you associate the Source transformation with a Db2 for z/OS CDC connection. You can define the connection in either Data Integration or Administrator. The PWX CDC Metadata Adapter then uses the connection to connect to the PowerExchange Listener on z/OS and retrieve extraction-map metadata for the Db2 source from the PowerExchange DTLCAMAP file.
    5. In the mapping, you must also define a Target transformation and connection and map the source fields to target fields.
  5. 5The Secure Agent in conjunction with Data Integration sends the extraction-map metadata to the Informatica Intelligent Cloud Services repository in the cloud.
  6. 6When you run the mapping task that is associated with the mapping, all of the CDC metadata, connection properties, mapping information, advanced source properties, CDC runtime properties, and advanced session properties are pushed down to the on-premises Secure Agent in the form of a session .xml file.
  7. 7The PWX CDC Reader on the Secure Agent machine communicates with the PowerExchange Listener on the PowerExchange Logger for Linux, UNIX, or Windows machine to retrieve the change records from the PowerExchange Logger log files.
  8. 8Data Integration transmits the change records to the mapped target.
Alternative configurations of PowerExchange with the Db2 for z/OS CDC Connector components and Cloud Data Integration are possible. For example: