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 PowerExchange Logger Configuration File for Remote Logging

For the PowerExchange Logger for Linux, UNIX, and Windows to log data from a remote source, you must customize the PowerExchange Logger configuration file on the system where the PowerExchange Logger log files will reside.

PowerExchange provides a sample configuration file, named pwxccl.cfg, in the PowerExchange installation directory. You can copy this file and customize the copy.

For a complete list of PowerExchange Logger configuration parameters, see the PowerExchange Logger for Linux, UNIX, and Windows chapter in the

PowerExchange CDC Guide for Linux, UNIX, and Windows

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

Parameter	Description
CAPTURE_NODE	Required for remote logging. The node name that the PowerExchange Logger uses to retrieve capture registrations and change data from the source system. This name must be defined in a NODE statement in the dbmover configuration file on the system where the PowerExchange Logger runs. The PowerExchange Logger uses this node name to connect to the PowerExchange Listener on the source system. This name should correspond to the node name in the LISTENER statement on the source system.
CAPTURE_NODE_EPWD or CAPTURE_NODE_PWD	Optional. An encrypted password (EPWD) or clear text password (PWD) that is associated with the user ID specified in the CAPTURE_NODE_UID parameter. If you specify CAPTURE_NODE_UID, you must specify either CAPTURE_NODE_EPWD or CAPTURE_NODE_PWD. However, do not specify both CAPTURE_NODE_EPWD and CAPTURE_NODE_PWD.
CAPTURE_NODE_UID	A user ID that controls PowerExchange Logger read access to capture registrations and change data on the remote node that is specified in the CAPTURE_NODE parameter. Whether this parameter is required depends on the operating system of the remote node and the SECURITY setting in the DBMOVER configuration file for the PowerExchange Listener on that node. If CAPTURE_NODE specifies a z/OS or i5/OS node that has a SECURITY setting of 0, do not specify this parameter. PowerExchange uses the user ID under which the PowerExchange Listener job runs to control access to capture registrations and change data. If CAPTURE_NODE specifies a z/OS or i5/OS node that has a SECURITY setting of 1, you must enter a valid operating system user ID for this parameter. Otherwise, error message PWX-00231 is issued, indicating a signon failure. However, PowerExchange uses the user ID under which the PowerExchange Listener job runs to control access to capture registrations and change data. If CAPTURE_NODE specifies a z/OS or i5/OS node that has a SECURITY setting of 2, you must enter a valid operating system user ID for this parameter. Otherwise, error message PWX-00231 is issued, indicating a signon failure. PowerExchange uses this user ID to control access to capture registrations and change data. If the specified user ID does not have the authority that is required to read capture registrations or change data, access fails. If CAPTURE_NODE specifies a Linux, UNIX, or Windows node, enter a user ID that is valid for the data source type: For Db2 sources on Linux, UNIX, or Windows, enter a valid operating system user ID that has Db2 DBADM or SYSADM authority. For Microsoft SQL Server instances that use SQL Server Authentication, enter a database user ID that permits access to the SQL Server distribution database. For a SQL Server instances that use Windows Authentication, PowerExchange uses the user ID under which the PowerExchange Listener was started. In this case, do not specify this parameter unless you want to specify another user. For MySQL sources on Linux or Windows, enter a database user ID that allows access to the MySQL binary logs. This user must have been granted the privileges that are required for MySQL CDC. For more information, see Preparing MySQL Sources. For Oracle sources, if you use PowerExchange Express CDC for Oracle, enter the ORACAPTL user ID that you defined, which permits access to the Oracle online and archive redo logs. For PostgreSQL sources, enter a database user ID that allows access to the replication store table in the source database and that has a user role with the REPLICATION attribute.
CONDENSENAME	Optional. A name for the command-handling service for a PowerExchange Logger for Linux, UNIX, and Windows process to which pwxcmd commands are issued. This service name must match the service name in the associated SVCNODE statement in the dbmover configuration file.
CONN_OVR	Recommended. The name of the override CAPI_CONNECTION statement to use for the PowerExchange Logger. If you do not enter CONN_OVR, the PowerExchange Logger uses the default CAPI_CONNECTION in the dbmover configuration file, if specified. Enter a valid CAPI_CONNECTION name for the source type. Informatica recommends that you specify CONN_OVR because it is the only type of override that the PowerExchange Logger can use.
DB_TYPE	Required. The source database type. Options are: ADA for Adabas sources. AS4 for Db2 for i (i5/OS) sources. DB2 for Db2 for z/OS sources. DCM for Datacom sources. IDL for IDMS log-based CDC sources. IMS for IMS sources. MSS for Microsoft SQL Server sources. MYS for MySQL sources. ORA for Oracle sources. PGS for PostgreSQL sources. UDB for Db2 sources on Linux, UNIX, or Windows. VSM for VSAM sources.
DBID	Required. A source identifier, sometimes called the `instance` name, that is defined in capture registrations. When used with DB_TYPE, it defines selection criteria for capture registrations in the CCT file. This value must match the instance or database name that is displayed in the Resource Inspector of the PowerExchange Navigator for the registration group that contains the capture registrations. Enter one of the following values based on the source type: For Adabas, enter the Instance name that is displayed for the registration group. For Datacom, enter the MUF Name value that is displayed for the registration group. Alternatively, if you use Datacom synchronous CDC, enter the value of the MUF parameter in the DTLINPUT data set specified in the MUF JCL. Or, if you use Datacom table-based CDC, enter the value of REG_MUF parameter in the ECCRDCMP member of the RUNLIB library. For Db2 for i (i5/OS), enter the Instance name that is displayed for the registration group. This name should match the INST parameter value in the AS4J CAPI_CONNECTION statement in the DBMOVER member of the CFG file. For Db2 on Linux, UNIX, or Windows, enter the Database name that is displayed for the registration group. For Db2 for z/OS, enter the Instance name that is displayed for the registration group. This name should match the RN parameter value in the Db2 statement in the RUNLIB(REPDB2OP) member. For IDMS Log-based CDC, enter the Logsid value that is displayed for the registration group. This value should match the LOGSID parameter value in the RUNLIB(ECCRIDLP) member. For IMS, enter the IMSID value that is displayed for the registration group. For IMS log-based CDC, this value should match the first parameter value in the IMSID statement in the RUNLIB(CAPTIMS) member. For Microsoft SQL Server, this value depends on whether you also specify the optional DISTSRV and DISTDB parameters in the PowerExchange Logger configuration file: If you specify the optional DISTSRV and DISTDB parameters, enter a name that serves as the collection identifier for all of the registrations. This name must be one to eight characters in length and start with a letter. This name overrides the instance name that is associated with the individual registrations. If you do not specify the DISTSRV and DISTDB parameters, enter the value that the PowerExchange Navigator generates and displays in the Instance field of the Resource Inspector for the registration group. For MySQL, enter the Instance name that is displayed for the registration group in the Resource Inspector . For Oracle, enter the Instance name that is displayed for the registration group. This value also should match the first positional parameter of the ORACLEID statement in the dbmover configuration file. For PostgreSQL, enter the Instance name that is displayed for the registration group in the Resource Inspector . For VSAM, enter the Instance name that is displayed for the registration group.
EXT_CAPT_MASK	Required. An existing directory path and a unique prefix to be used for generating the PowerExchange Logger log files.