CDC Guide for Linux, UNIX, and Windows

10.5
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Customizing the dbmover Configuration File on the System to Which Data Is Logged

For the PowerExchange Logger for Linux, UNIX, and Windows to log data from a remote Linux, UNIX, Windows,

i5/OS

, or z/OS source, you must customize the dbmover configuration file on the system where the PowerExchange Logger log files will reside.

PowerExchange provides a sample dbmover file in the PowerExchange installation directory. You can copy this file and customize the copy. For a complete list of all dbmover configuration statements, see the

PowerExchange Reference Manual

The following table describes the dbmover statements that are needed for remote logging:

Statement	Description
CAPT_PATH	Required. The path to the directory on the Linux, UNIX, or Windows system where the PowerExchange Logger CDCT file resides. The PowerExchange Logger stores information about its log files in the CDCT file. Each PowerExchange Logger that captures change data requires its own CDCT file.
CAPX CAPI_CONNECTION	Required. Parameters that the Consumer API (CAPI) uses for continuous extraction of change data from PowerExchange Logger for Linux, UNIX, and Windows log files. The DFLTINST parameter value in this statement must match the DBID value in the PowerExchange Logger configuration file, pwxccl.cfg.
LOGPATH	Optional. A unique path and directory for PowerExchange message log files on the Linux, UNIX, or Windows system where the PowerExchange Logger logs data in its log files.
NODE	Required. Information that PowerExchange uses to connect to the PowerExchange Listener on the source system from which change data is captured. This information includes a unique user-defined node name, the TCP/IP host name, and the port number. The node name that you enter in this statement must match the CAPTURE_NODE parameter value in the PowerExchange Logger configuration file.
Source-specific CAPI_CONNECTION	Required. A named set of parameters that the CAPI uses to connect to the change stream for a source type and control CDC processing. Copy the source-specific CAPI_CONNECTION statements from the DBMOVER configuration file on the source system. Use one of the following the statement types, as appropriate for the source from which you are remotely logging data: For Db2 for i (i5/OS) sources, use the AS4J and UOWC CAPI_CONNECTION statements. For Db2 sources on Linux, UNIX, and Windows, use UDB CAPI_CONNECTION statement. For Microsoft SQL Server sources, use the MSQL CAPI_CONNECTION statement. For MySQL sources, use the MYSQL CAPI_CONNECTION statement. For Express CDC for Oracle sources, use the ORAD CAPI_CONNECTION statement. For PostgreSQL sources, use the PG CAPI_CONNECTION statement. For z/OS sources, use the LRAP and UOWC CAPI_CONNECTION statements. Remove the z/OS -specific parameters from the UOWC statement.
SVCNODE	Optional. The TCP/IP port on which a command-handling service for a PowerExchange process, such as a PowerExchange Logger for Linux, UNIX, and Windows process, listens for pwxcmd commands.
TRACING	Optional. Enables PowerExchange alternative logging and specifies attributes for the alternative log files. PowerExchange uses the alternative log files instead of the default PowerExchange message log file to store messages.