Table of Contents

Search

  1. Preface
  2. Change Data Capture Introduction
  3. PowerExchange Listener
  4. PowerExchange Condense
  5. DB2 for i5/OS Change Data Capture
  6. Remote Logging of Data
  7. Introduction to Change Data Extraction
  8. Extracting Change Data
  9. Monitoring CDC Sessions
  10. Managing Change Data Extractions
  11. Tuning CDC Sessions
  12. Appendix A: DTL__CAPXTIMESTAMP Time Stamps

CDC Guide for i5/OS

CDC Guide for i5/OS

CAPI_CONNECTION Statements

CAPI_CONNECTION Statements

PowerExchange requires that you define CAPI_CONNECTION statements in the DBMOVER configuration file on any i5/OS system where PowerExchange captures or extracts change data. PowerExchange uses the parameters that you specify in the CAPI_CONNECTION statements to connect to the change stream and to customize capture and extraction processing.
For each data source type, you must define a specific type of CAPI_CONNECTION statement. For DB2 on i5/OS, define a AS4J CAPI_CONNECTION statement. You must also specify a UOWC CAPI_CONNECTION statement for the UOW Cleanser.
You can specify up to eight CAPI_CONNECTION statements in a dbmover.cfg file. You can identify one of the CAPI_CONNECTION statements for a specific data source type as the default. You can also specify overrides in various ways.
PowerExchange does not require CAPI_CONNECTION statements in the dbmover.cfg on the PowerExchange Navigator machine. You can register tables for CDC and perform database row tests on that machine because the PowerExchange Navigator can communicate with the PowerExchange Listener on the source machine where CDC occurs.

0 COMMENTS

We’d like to hear from you!