Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. PowerExchange Globalization
  12. Using the PowerExchange ODBC Drivers
  13. PowerExchange Datatypes and Conversion Matrix
  14. DTL__CAPXTIMESTAMP Time Stamps
  15. PowerExchange Glossary

Multiple CAPI Connections and Overrides

Multiple CAPI Connections and Overrides

PowerExchange can capture changes for more than one source type using a single PowerExchange Listener and DBMOVER configuration file on a single server.
You can define a maximum of eight CAPI_CONNECTION statements in a DBMOVER configuration file.
The CAPI_CONNECTION statements can be of the same type or of mixed types, as indicated by the TYPE parameter. The NAME parameter in each statement must specify a unique name.
If you define multiple CAPI_CONNECTION statements for a source type, you can optionally define a CAPI_SRC_DFLT statement to identify the default CAPI_CONNECTION for that source type. Also, you can optionally specify a CAPI_CONN_NAME parameter that specifies an overall default statement, out of all of the CAPI_CONNECTION statements defined in the DBMOVER file.
Instead of specifying defaults, you can use the following CAPI connection name overrides to point to a specific CAPI_CONNECTION statement:
  • For a CDC session, the
    CAPI Connection Name Override
    attribute in the PowerCenter PWX application connection.
  • For CAPXRT database row tests in the PowerExchange Navigator, the
    CAPI Connection Name
    value in the
    Advanced CAPXRT Parameters
    dialog box. If you add an SQL statement for generating restart tokens, include the CONNAME parameter to point to the override CAPI_CONNECTION.
  • If you use the DTLUAPPL to generate restart tokens, the CONN_OVR parameter in the DTLUAPPL control statement.
  • For the PowerExchange Logger for Linux, UNIX, and Windows, the CONN_OVR parameter in pwxccl.cfg configuration file.
  • For PowerExchange ODBC connections, the DTLCONN_OVR parameter in the odbc.ini file or the SQL escape sequence override DTLCONNOVR.
Informatica recommends that you use the following overrides:
  • If you extract change data from Linux, UNIX, and Windows sources, specify a
    CAPI Connection Name Override
    value in the application connections for your CDC sessions.
  • If you use the PowerExchange Logger for Linux, UNIX, and Windows, specify the CONN_OVR parameter in the pwxccl.cfg file.
The following example statements include multiple source-specific CAPI_CONNECTION statements for DB2 and Oracle, with an overall CAPI_CONN_NAME default and a CAPI_SRC_DFLT default for DB2:
CAPI_CONN_NAME=DTLUDB1 /* CAPI_CONNECTION=(NAME=DTLUDB1,TYPE=(UDB,CAPINAME=CAPIUDB1)) CAPI_CONNECTION=(NAME=CAPIUDB1,TYPE=(UDB, DATABASE=SAMPLE1,DBCONN=SAMPLE1,PASSWORD=user,USERID=password, CCATALOG=DTLCCATLAOG)) /* CAPI_CONNECTION=(NAME=DTLUDB2,TYPE=(UDB,CAPINAME=CAPIUDB2)) CAPI_CONNECTION=(NAME=CAPIUDB2,TYPE=(UDB, DATABASE=SAMPLE2,DBCONN=SAMPLE2,PASSWORD=password,USERID=user, CCATALOG=DTLCCATLAOG)) /* CAPI_CONNECTION=(NAME=DTLUDB,TYPE=(UDB,CAPINAME=CAPIUDB,)) CAPI_CONNECTION=(NAME=CAPIUDB,TYPE=(UDB, DATABASE=SAMPLE,DBCONN=SAMPLE,PASSWORD=password,USERID=user, CCATALOG=DTLCCATALOG)) CAPI_SRC_DFLT=(UDB,DTLUDB2) /* ORACLEID=(OEMCAP,OEMDB,OEMDB.INFORMATICA.COM,OEMDB.INFORMATICA.COM) CAPI_CONNECTION=(NAME=CAPIUOWC,TYPE=(UOWC,CAPINAME=CAPIORA)) CAPI_CONNECTION=(NAME=CAPIORA,TYPE=(ORCL,ORACOLL=OEMCAP))