MySQL CDC Connector > Introduction to MySQL 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 MySQL source tables and log them to PowerExchange Logger for Linux, UNIX, and Windows log files. Also, you must have a license that allows your organization to use the MySQL CDC Connector and PowerExchangeClient packages on a Linux or Windows system.
On each system from which you plan to use MySQL CDC Connector, you must install the Secure Agent. After you start the Secure Agent the first time, the MySQL CDC Connector and PowerExchangeClient components are installed locally. You then can use Cloud Data Integration, Administrator, and Monitor interfaces to configure MySQL CDC connections, mappings, and mapping tasks and to run and monitor mapping tasks.
The following image shows the general architecture of the MySQL CDC Connector components with Cloud Data Integration and a remote PowerExchange CDC and MySQL source system:
On-prem PowerExchange components and MySQL source in relation to on-prem MySQL 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 change capture process, PowerExchange Logger, and MySQL source reside on one Linux, UNIX, or Windows system and the MySQL CDC Connector components reside 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 reads change events, including data changes, for the source tables from the MySQL binary log by using the MySQL binary log reader, mysqlbinlog. PowerExchange captures change records for registered source tables and sends the change records to the PowerExchange Logger for Linux, UNIX, and Windows on a continuous basis.
  2. To capture change records, the PowerExchange capture process uses the capture registrations that are recorded in the PowerExchange CCT file. You defined a capture registration for each MySQL source table in the PowerExchange Navigator. The PowerExchange Navigator generated a corresponding extraction map, which will be used to extract the change records.
  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 MySQL CDC connection. You can define the connection in either Data Integration or Administrator. The PWX CDC Metadata Adapter then uses the MySQL CDC connection to connect to the PowerExchange Listener and retrieve extraction-map metadata for the MySQL source from the PowerExchange CAMAPS file.
  6. In the mapping, you must also define a Target transformation and connection and 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 MySQL CDC Connector components and Cloud Data Integration are possible. For example: