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

Order of Precedence for CAPI Statements and Overrides

Order of Precedence for CAPI Statements and Overrides

PowerExchange uses the following order of precedence when determining which CAPI connection information to use:
  1. CAPI connection name overrides take precedence over the CAPI_SRC_DFLT and CAPI_CONN_NAME statements.
  2. A CAPI_SRC_DFLT statement for a specific source type takes precedence over a CAPI_CONN_NAME statement for that source type.
  3. If you do not specify a CAPI connection name override or a CAPI_SRC_DFLT statement, PowerExchange uses the CAPI_CONN_NAME statement.
  4. If you do not specify a CAPI connection name override or CAPI_SRC_DFLT statement for the source, and a CAPI_CONN_NAME statement is also not available, PowerExchange uses the first CAPI_CONNECTION statement for the source type in the DBMOVER configuration file.
Informatica recommends that you specify a CAPI connection name override for the most efficient CAPI processing.