You must have a functional on-premises PowerExchange for IMS environment that can capture 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 Connector and PowerExchange Client packages on Linux and Windows.
On each system from which you plan to use IMS Connector, you must install the Secure Agent. After you start the Secure Agent the first time, the IMS Connector and PowerExchange Client components are installed locally. You then can use Cloud Data Integration, Administrator, and Monitor interfaces to configure IMS connections, mappings, and mapping tasks and to run and monitor mapping tasks.
The following image shows the general architecture of the IMS Connector components with Cloud Data Integration and a remote PowerExchange source system:
This configuration spans the following on-premises systems:
•The Windows system where the PowerExchange Navigator client runs.
•The z/OS system where the IMS database and PowerExchange Listener run.
•The system where the IMS Connector components and Secure Agent run.
Based on this configuration, the following processing occurs:
1PowerExchange retrieves records from IMS database and sends the data to the PowerExchange Listener for z/OS.
You defined a source transformation for each IMS source table in the PowerExchange Navigator. The PowerExchange Navigator generated a corresponding data map, which will be used to retrieve the records.
2When you design a mapping in Data Integration, you associate the Source transformation with a IMS connection. You can define the connection in either Data Integration or Administrator. The PWX Bulk Metadata Adapter then uses the connection to connect to the PowerExchange Listener on z/OS and retrieve metadata files for the IMS source from the PowerExchange Listener.
In the mapping, you must also define a Target transformation and connection and map the source fields to target fields.
3The Secure Agent in conjunction with Data Integration sends the metadata to the Informatica Intelligent Cloud Services repository in the cloud.
4When you run the mapping or mapping task, all of the metadata, connection properties, mapping information, advanced source properties, runtime properties, and advanced session properties are pushed down to the on-premises Secure Agent in the form of a session .xml file.
5The PWX Bulk Reader on the Secure Agent machine communicates with the PowerExchange Listener on the z/OS machine to retrieve the records from the PowerExchange Listener.
6Data Integration transmits the records to the mapped target.
