Search

User Guide

User Guide

1.1
- 1.3
- 1.2
- 1.0

Back Next

Preparing the PowerExchange Change Capture Environment

Preparing the PowerExchange Change Capture Environment

You must perform some PowerExchange configuration tasks for the PowerExchange CDC Publisher, even if you are already using PowerExchange to capture change data from data sources.

Perform some or all of the following configuration tasks:

Task	Reference
On the CDC Publisher machine, install a PowerExchange version that the CDC Publisher supports, unless you will run the CDC Publisher on an existing PowerExchange Navigator or PowerExchange Logger system.	Chapter "Installing and Upgrading PowerExchange on Linux and UNIX" or "Installing and Upgrading PowerExchange on Windows" in the PowerExchange Installation and Upgrade Guide
Ensure that a local copy of the PowerExchange license key file that includes the PowerExchange CDC Publisher option for the target messaging system exists. This PWX_LICENSE environment variable should point to this file.	-
In the PowerExchange Navigator, if capture registrations and extraction maps for the source tables or objects do not yet exist, create a capture registration for each source table or object. In the new registrations, set the Status option to Active and the Condense option to Part . The PowerExchange Navigator generates an extraction map for each capture registration that you create.	Chapters "Registration Groups and Capture Registrations" and "Extraction Groups and Extraction Maps" in the PowerExchange Navigator User Guide
On the PowerExchange CDC Publisher system, configure a dbmover configuration file that includes the following statements: A NODE statement that points to the PowerExchange Listener where the PowerExchange Logger for Linux, UNIX, and Windows runs. This node name must match the Extract.pwxNodeLocation property in the cdcPublisherPowerExchange.cfg file. If you use remote logging of change data to PowerExchange Logger log files, the node name must also match the CAPTURE_NODE value in the PowerExchange Logger configuration file, pwxccl.cfg. If the extraction maps and PowerExchange Logger are not on the same system, define another NODE statement that points to the system that contains the extraction maps. This node name must match the Extract.pwxXmapLocation property value in the cdcPublisherPowerExchange.cfg file. If the PowerExchange Listener or PowerExchange Logger is not on the same system as the CDC Publisher, optionally include a set of SVCNODE and CMDNODE statements for the Listener and for the Logger to be able to issue commands to these PowerExchange components from the local CDC Publisher system.	Chapter "DBMOVER Configuration" in the PowerExchange Reference Manual and the source-specific chapter in the PowerExchange CDC guide for your source platform.
On the PowerExchange Logger machine, configure a PowerExchange Logger configuration file, pwxccl.cfg, if one does not already exist. Also, in the dbmover configuration file on the PowerExchange Logger system, define a CAPX CAPI_CONNECTION statement for continuous extraction of change data from PowerExchange Logger log files.	Chapter "PowerExchange Logger for Linux, UNIX, and Windows" in the PowerExchange CDC Guide for Linux, UNIX, and Windows
If the PowerExchange data source is on IBM i or z/OS, configure remote logging of source data to PowerExchange Logger log files, if it is not already configured. If the data source is on a Linux, UNIX, or Windows machine, remote logging is optional.	Chapter "Remote Logging of Data" in the PowerExchange CDC Guide for Linux, UNIX, and Windows . Ignore steps related to the PowerCenter Integration Service and connection attributes.

PowerExchange Change Capture Environment

Watch

Comments

0 COMMENTS

We’d like to hear from you! Log in to comment.