PowerExchange uses some or all of the following components to perform its functions, depending on the system that you are using:
The graphical user interface from which you define and manage data maps, capture registrations, and extraction maps for the data sources from which you want to extract bulk data or capture change data. PowerExchange uses these definitions to determine the data sources to process. Capture registrations and extraction maps pertain to change data capture (CDC) only.
Manages data maps for nonrelational files and DB2 tables, and capture registrations and extraction maps for all data sources. The PowerExchange Listener maintains these definitions in the following files:
Data maps in the DATAMAPS file
Capture registrations in the CCT file
Extraction maps in the DTLCAMAP or CAMAPS file
The PowerExchange Listener also handles extraction requests for bulk data and change data.
If a data source or data target is remote from the system on which you are using PowerExchange, you must also run a PowerExchange Listener on the remote data source or target to communicate with PowerExchange.
On a z/OS system, provides capture registration information to the following ECCRs during CDC:
Other ECCRs read capture registration information directly from the CCT data set. For all of the ECCRs, the PowerExchange Agent verifies the capture registration information.
The PowerExchange Agent also manages global queues and data flow among various PowerExchange CDC components.
PowerExchange Logger for Linux, UNIX, and Windows
On a Linux, UNIX, or Windows machine, optionally writes change data from the change stream to PowerExchange Logger log files. PowerExchange then extracts the change data from the PowerExchange Logger log files rather than from the source database or log files. A PowerExchange Logger process can operate in either continuous mode or batch mode.
PowerExchange Logger for z/OS
On a z/OS system, receives captured change data from the PowerExchange Environmental Change Capture Routines (ECCR) that are connected to it and stores the change data in log data sets. The change data is then available for real-time extractions or PowerExchange Condense jobs.
On a z/OS system, captures change data from a data source and passes the captured changes to the PowerExchange Logger for recording. PowerExchange provides an ECCR for each type of data source. Depending on the source type, the ECCR captures changes synchronously as they are made or asynchronously from database logs.
On i5/OS or z/OS, optionally creates condense files that contain a condensed version of the change data in the change stream. If you use this optional feature, PowerExchange extracts change data from condense files rather than from log files. You can run multiple Condense jobs at a time.