Table of Contents

Search

  1. Preface
  2. PowerExchange Navigator Introduction
  3. Data Maps
  4. Data Maps for Specific Data Sources
  5. Copybooks
  6. Registration Groups and Capture Registrations
  7. Extraction Groups and Extraction Maps
  8. Personal Metadata
  9. Database Row Test
  10. PowerExchange Navigator Examples
  11. Appendix A: PowerExchange Functions for User-Defined Fields
  12. Appendix B: User Access Method Programs
  13. Appendix C: Application Groups and Applications
  14. Appendix D: Data Map Properties
  15. Appendix E: Record, Field, and Table Properties
  16. Appendix F: DTL__CAPXTIMESTAMP Time Stamps
  17. Appendix G: Trace for Creating a Memory Map When Importing a COBOL Copybook

Navigator User Guide

Navigator User Guide

Viewing or Editing Properties for an Extraction Group

Viewing or Editing Properties for an Extraction Group

You can view or edit properties for an extraction group.
You might edit the properties for an extraction group to change its name, location, or the user ID and password used to access the source. You cannot change the database type for an extraction group.
  1. Open the extraction group.
    The
    Extraction Group
    tab in the
    Resource Inspector
    displays the following properties for the extraction group, depending the source type:
    Property
    Description
    Name
    A user-defined name for the extraction group.
    Access Method
    Read-only. Access method associated with the data source type.
    Location
    Location of the source for which you want to capture changes.
    UserID
    A user ID that allows access to the source. The type of user ID depends on the source type and PowerExchange security settings:
    • If the source is on an i5/OS or z/OS system and PowerExchange security is enabled, enter an operating system user ID. PowerExchange security is enabled when the PowerExchange SECURITY statement in the DBMOVER member is set to (1,
      x
      ) or 2.
      x
      ).
    • For a DB2 LUW, Microsoft SQL Server, MySQL, Oracle, or PostgreSQL source, enter a valid database user ID, if required. For more information, see the SECURITY Statement in the
      PowerExchange Reference Manual
      .
    • For a source on a supported Linux, UNIX, or Windows system, if you have enabled PowerExchange LDAP user authentication and, if applicable, disabled relational pass-through authentication, the user ID is the enterprise user name. For more information, see the
      PowerExchange Reference Manual
      .
    Password
    A password for the specified user ID.
    If the data source is on an i5/OS or z/OS system, 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. 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. PowerExchange 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
    .
    Instance
    The instance name from the registration group.
    For an Adabas, DB2 for i5/OS, Oracle, or VSAM source, the instance name is the collection identifier.
    For a DB2 for z/OS source, the instance name is the database instance name.
    For a Microsoft SQL Server source, the instance name is the
    Instance
    value that you entered when creating the registration group. If you did not enter an instance name, this value is a generated value that is composed of the first four characters of the database name followed by an ascending number, which starts at 000.
    For a MySQL or PostgreSQL source, the instance name is the
    Instance
    value that you entered when creating the registration group. If you did not enter an instance name, this value is a generated value that consists of the first four characters of the database server name followed by an ascending number, which starts at 000.
    MUF Name
    For a CA Datacom/DB source, the name of the Multi-User Facility (MUF).
    Server
    For a Microsoft SQL Server source, the name of the publication server. For a PostgreSQL source, the name of the database server.
    MySQL Server
    For a MySQL source, the name of the database server.
    Database
    For a DB2 LUW, Microsoft SQL Server, or PostgreSQL source, the name of the source database.
    DB Name
    For an IDMS log-based source, the name of the database.
    Recon ID
    For an IMS source, the RECON identifier for the database.
    Oracle SID
    Read-only. For an Oracle source, the system identifier (SID) for the database.
  2. To edit a property, click the property box in the
    Resource Inspector
    and enter a value.
    After you edit a property, a red square appears next to the changed property.
    To undo a change before you apply it, click
    Reset
    .
  3. To apply a change, click
    Apply
    .
    If you edit the extraction group name, you are prompted to confirm the change. If the new name matches the name of an existing extraction group, you are prompted to overwrite the existing group.
    If you edit the location, PowerExchange displays an error message if the location is not valid for the instance.
    If you edit the instance, PowerExchange displays an error message if the specified instance does not exist.
  4. To confirm the changes, click
    Yes
    .
    The
    Resource Inspector
    updates the fields that you edited.

0 COMMENTS

We’d like to hear from you!