Integration with the PowerExchange CDC environment
You must have a functional on-premises PowerExchange CDC for IMS environment that can capture change records from IMS source tables and log the changes to PowerExchange Logger log files. Also, you must have a license that allows your organization to use the IMS CDC Connector and PowerExchange Client packages on Linux and Windows.
On each system from which you plan to use IMS CDC Connector, you must install the Secure Agent. After you start the Secure Agent the first time, the IMS CDC Connector and PowerExchange Client components are installed locally. You then can use Cloud Data Integration, Administrator, and Monitor interfaces to configure IMS CDC connections, mappings, and mapping tasks and to run and monitor mapping tasks.
The following image shows the general architecture of the IMS CDC Connector components with Cloud Data Integration and a remote PowerExchange CDC source system:
In this configuration, the PowerExchange IMS CDC environment resides on a z/OS system and the IMS CDC Connector environment resides on a Linux or Windows system. The PowerExchange Navigator runs on a Windows system apart from both environments. Based on this image, the following processing occurs:
1PowerExchange CDC for IMS actively captures change records from IMS logs and sends the records to the PowerExchange Logger on a continuous basis.
To capture change records, PowerExchange uses the capture registrations and extractions maps that you defined in the PowerExchange Navigator for the IMS source tables.
2The PowerExchange Logger logs the change records in its log files.
The pwxccl.cfg file defines the PowerExchange Logger configuration.
3When you design a mapping in Data Integration, you associate the Source transformation with a IMS CDC connection. You can define the connection in either Data Integration or Administrator. The PWX CDC Metadata Adapter then uses the IMS CDC connection to connect to the PowerExchange Listener and retrieve extraction-map metadata for the IMS source from the PowerExchange CAMAPS file.
In the mapping, you must also define a Target transformation and connection and then map the source fields to target fields.
4The Secure Agent in conjunction with Data Integration sends the extraction-map metadata to the Informatica Intelligent Cloud Services repository in the cloud.
5When 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.
6The PWX CDC Reader on the Secure Agent machine communicates with the PowerExchange Listener to retrieve the change records from PowerExchange Logger log files.
7Data Integration transmits the change records to the mapped target.
Alternative configurations of PowerExchange with the IMS CDC Connector components and Cloud Data Integration are possible. For example:
•The CDC Connector components, and Secure Agent can run on the same Linux or Windows system.
•The PowerExchange Logger for Linux, UNIX, and Windows and its log files can reside on a system that is remote from the IMS source system and remote from the Linux or Windows system where the IMS CDC Connector components and Secure Agent run. By logging change data to a remote PowerExchange Logger, you can reduce resource consumption on the source system and possibly reduce the network overhead of data transfer. For more information, see "Remote Logging of Data" in the PowerExchange CDC Guide for z/OS.
•The PowerExchange Navigator can run on any supported Windows system, including a Windows system where the IMS database or Secure Agent runs.
