Db2 for LUW CDC Connector > Introduction to Db2 for LUW CDC Connector > Integration with the PowerExchange CDC environment
  

Integration with the PowerExchange CDC environment

You must have a functional on-premises PowerExchange CDC for Db2 environment that can capture change records from Db2 for LUW source tables and log the changes to PowerExchange Logger for Linux, UNIX, and Windows log files. Also, you must have a license that allows your organization to use the Db2 for LUW CDC Connector and PowerExchange Client packages on Linux and Windows.
On each system from which you plan to use Db2 for LUW CDC Connector, you must install the Secure Agent. After you start the Secure Agent the first time, the Db2 for LUW CDC Connector and PowerExchange Client components are installed locally. You then can use Cloud Data Integration, Administrator, and Monitor interfaces to configure Db2 for LUW CDC connections, mappings, and mapping tasks and to run and monitor mapping tasks.
The following image shows the general architecture of the Db2 for LUW CDC Connector components with Cloud Data Integration and a remote PowerExchange CDC source system:
On-prem PowerExchange components and Oracle source in relation to on-prem Db2 LUW CDC Connector and Data Integration components on a separate system. Shows data flow from the source to target and source metadata flow to the cloud repository.
In this configuration, the PowerExchange Db2 CDC environment resides on one Linux, UNIX, or Windows system and the Db2 for LUW CDC Connector environment resides on another Linux or Windows system. The PowerExchange Navigator runs on a Windows system apart from both environments. Based on this image, the following processing occurs:
  1. 1. PowerExchange CDC for Db2 for LUW actively captures change records from Db2 archive logs and sends the records to the PowerExchange Logger for Linux, UNIX, and Windows on a continuous basis.
  2. To capture change records, PowerExchange uses the capture registrations and extractions maps that you defined in the PowerExchange Navigator for the Db2 source tables.
  3. 2. The PowerExchange Logger logs the change records in its log files.
  4. The pwxccl.cfg file defines the PowerExchange Logger configuration.
  5. 3. When you design a mapping in Data Integration, you associate the Source transformation with a Db2 for LUW CDC connection. You can define the connection in either Data Integration or Administrator. The PWX CDC Metadata Adapter then uses the Db2 for LUW CDC connection to connect to the PowerExchange Listener and retrieve extraction-map metadata for the Db2 source from the PowerExchange CAMAPS file.
  6. In the mapping, you must also define a Target transformation and connection and then map the source fields to target fields.
  7. 4. The Secure Agent in conjunction with Data Integration sends the extraction-map metadata to the Informatica Intelligent Cloud Services repository in the cloud.
  8. 5. When 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.
  9. 6. The PWX CDC Reader on the Secure Agent machine communicates with the PowerExchange Listener to retrieve the change records from PowerExchange Logger log files.
  10. 7. Data Integration transmits the change records to the mapped target.
Alternative configurations of PowerExchange with the Db2 for LUW CDC Connector components and Cloud Data Integration are possible. For example: