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. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  15. Appendix B: PowerExchange Glossary

CAPXRT Properties Tab

CAPXRT Properties Tab

On the
CAPXRT Properties
tab in the
PowerExchange Data Source
wizard, enter properties to define a PowerExchange CAPXRT data source.
Extract Type
The extraction type. The options are:
  • SL
    . Extracts all data since the last extraction.
  • RS
    . Restarts the previous, or a specified, extraction.
Corresponding ODBC Parameter: CAPXTYPE
Image Type
The image type. The options are:
  • BA
    . Captures the before image data, before the latest change, and the after image data, after the latest change. The before image data is shipped with an action character forcing the deletion of the record. The after image data, which includes the change data, is in the format of an insert operation.
  • AI
    . Captures the after image data only.
  • TU
    . Captures the before and after image data, as it occurs. The before image data enables the application to ensure that no changes occurred in the record since the request. The after image data appears as an update operation. The update is a full image, but the application that captures this change can change the target record rather than delete it and insert a new record, as occurs with a BA.
Corresponding ODBC Parameter: CAPXIMAGETYPE
AS400 Library/Filename
Overrides the fully qualified DB2 for i5/OS library and table name specified in the PowerExchange capture registration.
For example:
STQA/NEWTABLE
Corresponding ODBC Parameter: DBQUAL1
AS400 Library/Journal
Overrides the fully qualified library and journal name specified in the PowerExchange capture registration.
For example:
STQA/NEWJOURNAL
Corresponding ODBC Parameter: UAP
Oracle Instance
Overrides the Oracle instance value in the second positional parameter in the ORACLEID statement in the dbmover.cfg configuration file. For example:
ORACLEID=(
coll_id
,
oracle_sid
,
connect_string
,
cap_connect_string
)
Used in conjunction with the
Oracle Connection String
value to enable the use of a single set of capture registrations to capture data from multiple Oracle instances.
If you specify an
Oracle Instance
value, but no
Oracle Connection String
value, Oracle capture uses the Oracle connection string value specified in the ORACLEID statement in the dbmover.cfg file.
Corresponding ODBC Parameter: ORAINST
Oracle Connection String
Overrides the Oracle connection string value in the third positional parameter in the ORACLEID statement in the dbmover.cfg configuration file. For example:
ORACLEID=(
coll_id
,
oracle_sid
,
connect_string
,
cap_connect_string
)
Used in conjunction with the
Oracle Instance
value to enable the use of a single set of capture registrations to capture data from multiple Oracle instances.
If you specify an
Oracle Connection String
value, but no
Oracle Instance
value, Oracle capture uses the Oracle connection string value specified in the ORACLEID statement in the dbmover.cfg file.
Corresponding ODBC Parameter: ORACONN
Oracle Schema
Overrides the Oracle schema value in a PowerExchange registration group to enable the use of a single set of capture registrations to capture data from multiple schemas that might exist in an Oracle instance.
Corresponding ODBC Parameter: ORASCHEMA
DB2 UDB Database
For DB2 for Linux, UNIX, and Windows only. Overrides the database connection value specified in the PowerExchange extraction map.
Corresponding ODBC Parameter: DATABASE
CAPI Connection
Overrides the default database connection specified in a CAPI_CONNECTION statement in the DBMOVER configuration file.
To point to the relevant data source, use the value that is specified in the NAME parameter of the CAPI_CONNECTION statement in the DBMOVER configuration file.
Corresponding ODBC Parameter: DTLCONN_OVR
Extraction Schema
Overrides the schema name specified in a PowerExchange extraction map.
Maximum length is 128 characters. No spaces allowed.
Corresponding ODBC Parameter: XTRASCHEMA