Sequential File Connector > Introduction to Sequential File Connector > Integration with the PowerExchange environment
  

Integration with the PowerExchange environment

You must have a functional on-premises PowerExchange environment that can retrieve records from sequential source data sets on a z/OS system. The Sequential File Connector retrieves records by using the data map metadata.
PowerExchange, in conjunction with Data Integration, can move bulk data from sequential data sets on z/OS or files on i5/OS, Linux, UNIX, or Windows. These types of sources and targets use the SEQ access method. Hereafter, the term sequential file is used to refer to sequential data sets on z/OS and files on i5/OS, Linux, UNIX, or Windows systems.
You must have a license that allows your organization to use the Sequential File Connector and PowerExchangeClient packages on a Linux and Windows system. On each system from which you plan to use Sequential File Connector, install the Secure Agent. After you start the Secure Agent the first time, the Sequential File Connector and PowerExchangeClient package are installed locally. You then can use Cloud Data Integration, Administrator, and Monitor interfaces to configure Sequential connections, mappings, and mapping tasks and to run and monitor mapping tasks.
The following image shows the general architecture of the Sequential File Connector components in relation to Cloud Data Integration and the remote source system:
This configuration spans the following on-premises systems:
Based on this configuration, the following processing occurs:
  1. 1You defined a data map for each Sequential Data Set in the PowerExchange Navigator. The data map provides a relational type view of the records. It is used to provide metadata and data access.
  2. 2When you design a mapping in Data Integration, you associate the Source transformation with a Sequential File 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 and retrieve data map metadata files for the source from the PowerExchange Listener.
  3. In the mapping, you must also define a Target transformation and connection and map the source fields to target fields.
  4. 3The Secure Agent in conjunction with Data Integration sends the data map metadata to the Informatica Intelligent Cloud Services repository in the cloud.
  5. 4When you run the mapping task that is associated with the mapping, 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.
  6. 5The PWX Bulk Reader on the Secure Agent machine communicates with the PowerExchange Listener to retrieve the records from the PowerExchange Listener.
  7. 6Data Integration transmits the records to the mapped target.
Alternative configurations of PowerExchange with the Sequential File Connector components and Cloud Data Integration are possible. For example: