Datacom Connector Guide > Introduction to Datacom Connector > Integration with the PowerExchange environment
  

Integration with the PowerExchange environment

You must have a functional on-premises PowerExchange environment that can replicate data from Datacom source tables on a z/OS system and transmit the data to a supported target.
You must have a license that allows your organization to use the Datacom Connector and PowerExchange Client packages on a Linux or Windows system. On each system from which you plan to use Datacom Connector, install the Secure Agent. After you start the Secure Agent the first time, the Datacom Connector and PowerExchange Client package are installed locally. You then can use Cloud Data Integration, Administrator, and Monitor interfaces to configure Datacom connections, mappings, and mapping tasks and to run and monitor mapping tasks.
The following image shows the general architecture of the Datacom Connector components in relation to Cloud Data Integration, the remote Datacom source system:
This configuration spans the following on-premises systems:
Based on this configuration, the following processing occurs:
  1. 1PowerExchange reads from Datacom tables where the PowerExchange Listener for z/OS resides.
  2. You defined a source transformation for each Datacom source table in the PowerExchange Navigator. The PowerExchange Navigator generated a corresponding data map, which will be used to retrieve the records.
  3. 2When you design a mapping in Data Integration, you associate the Source transformation with a Datacom 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 read from Datacom tables.
  4. In the mapping, you must also define a Target transformation and connection and map the source fields to target fields.
  5. 3The Secure Agent in conjunction with Data Integration sends the Datacom metadata to the Informatica Intelligent Cloud Services repository in the cloud.
  6. 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.
  7. 5The PWX Bulk Reader on the Secure Agent machine communicates with the PowerExchange Listener on the z/OS machine to move bulk data from the source tables.
  8. 6Data Integration transmits the records to the mapped target.