CDC Guide for i5/OS

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

Back Next

Example of Remote Logging from a Db2 for i Data Source

In this example, you use a PowerExchange Logger for Linux, UNIX, and Windows instance on a UNIX system to capture change data from Db2 for i journal receivers on i5/OS. The system where the PowerExchange Logger runs is separate from the PowerCenter Integration Service system where you run CDC sessions.

You need the PowerExchange Logger to capture change data for registered tables from Db2 journals in the Db2 instance PROD2 and then log that data to its log files on the remote UNIX system. To do so, you must customize a PowerExchange Logger configuration file on the UNIX system and the dbmover configuration files on both the i5/OS and UNIX systems. Also, for the PowerCenter CDC sessions to extract change data from the PowerExchange Logger log files on UNIX, you must add NODE statements for the source and PowerExchange Logger systems to the dbmover configuration file on the Integration Service system and configure some PWXPC connection attributes.

First install PowerExchange on all three systems. You must run a PowerExchange Listener on the source system and on the PowerExchange Logger system. A PowerExchange Listener is not required on the PowerCenter Integration Service system.

On the i5/OS source system, ensure that the DBMOVER member in the

datalib/CFG

library includes the following CAPI_CONNECTION statements:

LISTENER=(i50S1,TCPIP,2480)
/* UOW Cleanser CAPI Connection
CAPI_CONNECTION=(NAME=i5UOWC,TYPE=(UOWC,CAPINAME=i5_AS4J,RSTRADV=600,MEMCACHE=20480))
/* DB2 for i5/OS CAPI Connection
CAPI_CONNECTION=(NAME=i5_AS4J,TYPE=(AS4J,JOURNAL=(JRN=PRODDATA/PRODJRN),
INST=PROD2,EOF=N,STOPIT=(CONT=5),LIBASUSER=Y))

In the AS4J CAPI_CONNECTION statement, the INST parameter value must match the

Instance

name that is displayed for the registration group in the PowerExchange Navigator.

On the UNIX system with the PowerExchange Logger log files, ensure that the dbmover configuration file includes the following statements:

/*
/* dbmover
/*
LISTENER=(unix2,TCPIP,2480)
NODE=(unix1,TCPIP,prod2,2480)
...
LOGPATH=/pwx/logs/i5oscond
CAPT_XTRA=/pwx/capture/i5oscond/camaps
CAPT_PATH=/pwx/capture/i5oscond
/*
/* Source-specific CAPI Connection
CAPI_CONNECTION=(NAME=i5UOWC,TYPE=(UOWC,CAPINAME=i5_AS4J,RSTRADV=600,MEMCACHE=20480))
CAPI_CONNECTION=(NAME=i5_AS4J,TYPE=(AS4J,JOURNAL=(JRN=PRODDATA/PRODJRN),INST=PROD2,EOF=N,STOPIT=(CONT=5),LIBASUSER=Y))
/*
/* CAPX CAPI Connection for continuous extraction
CAPI_CONNECTION=(NAME=CAPXPROD,TYPE=(CAPX,DFLTINST=PROD2,FILEWAIT=60,RSTRADV=600))

In the CAPX CAPI_CONNECTION, the DFLTINST value is the name that is displayed in the

Instance

field for the registration group in the PowerExchange Navigator.

You can use the JOURNAL parameter to specify journal overrides for specific extraction operations where you need to process changes from a range of journal receivers outside of default processing.

On the UNIX system with the PowerExchange Logger system log files, customize the PowerExchange Logger configuration file, pwxccl.cfg. For this example, include the following statements:

/*
/* pwxccl 
/*
DBID=PROD2 
DB_TYPE=AS4
CONN_OVR=i5UOWC
CAPTURE_NODE=i5OS1
CAPTURE_NODE_UID=db2user
CAPTURE_NODE_EPWD=encrypted_password
PROMPT=Y
EXT_CAPT_MASK=/pwx/capture/i5oscond/condense  
COND_CDCT_RET_P=50
LOGGER_DELETES_EXPIRED_CDCT_RECORDS=Y 
COLL_END_LOG=0 
NO_DATA_WAIT=0
NO_DATA_WAIT2=10  
FILE_SWITCH_VAL=20000 
FILE_SWITCH_CRIT=R 
CAPT_IMAGE=BA

The CAPTURE_NODE parameter points to the source system node where the PowerExchange Listener processes capture requests.

Start the PowerExchange Listener and PowerExchange Logger for Linux, UNIX, and Windows on the UNIX system. Verify that the PowerExchange Listener is also running on the i5/OS system.

On the PowerCenter Integration Service system, add the following NODE statements to the dbmover file:

A NODE statement that points to the PowerExchange Listener on the source system

A NODE statement that points to the UNIX system with the PowerExchange Logger log files

This example uses the following NODE statements in the dbmover file on the PowerCenter Integration Service system:

NODE=(i5OS1,TCPIP,i5OS1,2480)
NODE=(unix2,TCPIP,prod2,2480)

Create a PowerCenter mapping, session, and workflow.

Configure a PWX DB2i5OS CDC Real Time application connection for CDC sessions that extract change data from the PowerExchange Logger log files on the UNIX system.

For this example, set the following connection attributes:

For the

Location

attribute, enter unix2 to point to the node where the PowerExchange Logger for Linux, UNIX, and Windows log files reside. CDC sessions will read data from this location.

For the

Map Location

attribute, enter i5OS1 to point to the location of the extraction maps, which is the source system node.

For the

Map Location User

attribute, enter a valid user ID for the map location.

For the

Map Location Password

attribute, enter the password for the map location user.

For the

CAPI Connection Name

attribute, enter CAPXPROD to indicate the CAPX CAPI_CONNECTION statement to use.

Cold start the CDC session.

The session begins extracting change data from the PowerExchange Logger log files on the UNIX system.

Rename Saved Search

Table of Contents

CDC Guide for i5/OS

CDC Guide for i5/OS

Example of Remote Logging from a Db2 for i Data Source

Example of Remote Logging from a Db2 for i Data Source