Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: PowerExchange Client for PowerCenter (PWXPC)
  4. Part 3: PowerExchange ODBC
  5. Appendix A: PowerExchange Interfaces for PowerCenter Tips
  6. Appendix B: Datatypes and Code Pages
  7. Appendix C: PowerExchange Interfaces for PowerCenter Troubleshooting

PowerExchange Interfaces for PowerCenter

PowerExchange Interfaces for PowerCenter

Working with Extraction Map Definitions

Working with Extraction Map Definitions

You can import the PowerExchange extraction maps for CDC sources, instead of importing the source table metadata from the database, to create source definitions. The source definitions can then be included in mappings.
For CDC, the use of extraction maps is recommended for the following reasons:
  • Source extraction maps can contain a subset of the source columns to reduce capture processing.
  • Extraction maps contain the PowerExchange-generated columns, such as DTL__CAPXTIMESTAMP and DTL__CAPXACTION, and DTL__BI, which provided information needed for CDC.
  1. To import an extraction map for a CDC source definition, click
    Sources
    Import from PowerExchange
    .
    For nonrelational source types, the dialog box and parameters are the same.
  2. In the
    Import from PowerExchange
    dialog box, enter the following information:
    Attribute
    Required or Optional
    Description
    Location
    Required
    The node name of the PowerExchange Listener. This value must match the node name in a NODE statement in the PowerExchange DBMOVER configuration file on the system where the database resides.
    User Name
    Required
    A user name that has the authority to connect to the source database.
    For sources on supported Linux, UNIX, or Windows systems, if you have enabled PowerExchange LDAP user authentication, the user name is the enterprise user name. For more information, see the
    PowerExchange Reference Manual
    .
    Password
    Required
    A password for the specified user. Passwords that are less than nine characters in length are not validated.
    To avoid errors that might arise due to code page differences, Informatica recommends that the password includes only those characters that are allowed for passphrases.
    For access to i5/OS or z/OS, you can enter a valid PowerExchange passphrase instead of a password. An i5/OS passphrase can be from 9 to 31 characters in length. A z/OS passphrase can be from 9 to 128 characters in length when using PWXPC. A passphrase can contain the following characters:
    • Uppercase and lowercase letters
    • The numbers 0 to 9
    • Spaces
    • The following special characters:
      ’ - ; # \ , . / ! % & * ( ) _ + { } : @ | < > ?
      The first character is an apostrophe.
    Passphrases cannot include single quotation marks (‘), double quotation marks (“), or currency symbols.
    On z/OS, the allowable characters in the IBM IRRPHREX exit do not affect the allowable characters in PowerExchange passphrases.
    On z/OS, a valid RACF passphrase can be up to 100 characters in length. PWXPC truncates passphrases longer than 100 characters when passing them to RACF for validation.
    To use passphrases, ensure that the PowerExchange Listener runs with a security setting of SECURITY=(1,N) or higher in the DBMOVER member. For more information, see "SECURITY Statement" in the
    PowerExchange Reference Manual
    .
    Multi-Record Datamaps
    -
    Select this option to list multi-record data maps. SEQ or VSAM sources only.
    Source Type
    Required
    Select one of the following source types:
    • ADABAS
    • DATACOM
    • DB2zOS
    • DB2i5OS
    • DB2LUW
    • IDMS
    • IMS
    • MSSQL
    • MYSQL
    • ORACLE
    • POSTGRESQL
    • VSAM
    CDC Datamaps
    Required
    Select this option to list CDC extraction maps.
    Network Timeout
    Optional
    The number of seconds that must elapse during a network send or receive operation before PowerExchange ends the connection and issues a timeout error message.
    Schema
    Optional
    A schema name that is used to filter the extraction maps.
    Map name
    Optional
    A map name that is used to filter the extraction maps.
    Respect Case
    Optional
    Select this option to have PowerExchange treat the schema and map name filter values in a case-sensitive manner when searching for extraction maps. When this option is cleared, PowerExchange ignores the case of the filter values.
  3. Optionally, define filter criteria to filter the list schemas and tables that are displayed. You can enter a schema name, a table name, or both.
    In the filter criteria, you can include the following wildcard characters to create a mask:
    • *
      (asterisk). Represents one or more characters.
    • ?
      (question mark). Represents one character.
    For example:
    • A*
      displays schemas and tables that begin with an A.
    • *A
      displays schemas and tables that end with an A.
    • *cust*
      displays schemas that contain “cust.”
  4. Click
    Connect
    .
    The Designer displays a list of extraction maps to import in the
    Selected Datamaps
    box. The extraction maps are filtered based on the source type . If no tables are found, “No Data Found” displays.
  5. Select the extraction map or maps that you want to import.
    To select multiple extraction maps, use the Shift key or Ctrl key or click
    Select all
    .
  6. Click
    OK
    .
    The source definition appears in the workspace. The Designer uses the extraction map name as the name of the source definition.
In Designer, if you use the
Import from PowerExchange
option to import a Db2 LUW extraction map for a source that has long table and column names, some column names might not be displayed or long column names might be truncated to 74 characters without any warning or error message. Alternatively, if you use the
Import from PowerExchange
option to import table definitions from the Db2 catalog for a source or target table that has table or column names longer than 80 characters, Designer displays a message that indicates the table name or column name is too long and the import fails.

0 COMMENTS

We’d like to hear from you!