Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Content Management Service
  4. Data Integration Service
  5. Data Integration Service Architecture
  6. Data Integration Service Management
  7. Data Integration Service Grid
  8. Data Integration Service Applications
  9. Metadata Manager Service
  10. Model Repository Service
  11. PowerCenter Integration Service
  12. PowerCenter Integration Service Architecture
  13. High Availability for the PowerCenter Integration Service
  14. PowerCenter Repository Service
  15. PowerCenter Repository Management
  16. PowerExchange Listener Service
  17. PowerExchange Logger Service
  18. SAP BW Service
  19. Search Service
  20. System Services
  21. Test Data Manager Service
  22. Web Services Hub
  23. Application Service Upgrade
  24. Application Service Databases
  25. Connecting to Databases from Windows
  26. Connecting to Databases from UNIX
  27. Updating the DynamicSections Parameter of a DB2 Database

Configuring Native Connectivity

Configuring Native Connectivity

You can configure native connectivity to an IBM DB2 database to increase performance.
The following steps provide a guideline for configuring native connectivity. For specific instructions, see the database documentation.
  1. To configure connectivity on the machine where the Data Integration Service, PowerCenter Integration Service, or PowerCenter Repository Service process runs, log in to the machine as a user who can start a service process.
  2. Set the DB2INSTANCE, INSTHOME, DB2DIR, and PATH environment variables.
    The UNIX IBM DB2 software always has an associated user login, often db2admin, which serves as a holder for database configurations. This user holds the instance for DB2.
    DB2INSTANCE
    . The name of the instance holder.
    Using a Bourne shell:
    $ DB2INSTANCE=db2admin; export DB2INSTANCE  
    Using a C shell:
    $ setenv DB2INSTANCE db2admin   
    INSTHOME
    . This is db2admin home directory path.
    Using a Bourne shell:
    $ INSTHOME=~db2admin
    Using a C shell:
    $ setenv INSTHOME ~db2admin>
    DB2DIR
    . Set the variable to point to the IBM DB2 CAE installation directory. For example, if the client is installed in the /opt/IBM/db2/V9.7 directory:
    Using a Bourne shell:
    $ DB2DIR=/opt/IBM/db2/V9.7; export DB2DIR
    Using a C shell:
    $ setenv DB2DIR /opt/IBM/db2/V9.7
    PATH
    . To run the IBM DB2 command line programs, set the variable to include the DB2 bin directory.
    Using a Bourne shell:
    $ PATH=${PATH}:$DB2DIR/bin; export PATH
    Using a C shell:
    $ setenv PATH ${PATH}:$DB2DIR/bin
  3. Set the shared library variable to include the DB2 lib directory.
    The IBM DB2 client software contains a number of shared library components that the Data Integration Service, PowerCenter Integration Service, and PowerCenter Repository Service processes load dynamically. Set the shared library environment variable so that the services can find the shared libraries at run time.
    The shared library path must also include the Informatica installation directory
    (server_dir)
    .
    Set the shared library environment variable based on the operating system.
    The following table describes the shared library variables for each operating system:
    Operating System
    Variable
    Solaris
    LD_LIBRARY_PATH
    Linux
    LD_LIBRARY_PATH
    AIX
    LIBPATH
    For example, use the following syntax for Solaris and Linux:
    • Using a Bourne shell:
      $ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/
      server_dir
      :$DB2DIR/lib; export LD_LIBRARY_PATH
    • Using a C shell:
      $ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/
      server_dir
      :$DB2DIR/lib
    For AIX:
    • Using a Bourne shell:
      $ LIBPATH=${LIBPATH}:$HOME/
      server_dir
      :$DB2DIR/lib; export LIBPATH
    • Using a C shell:
      $ setenv LIBPATH ${LIBPATH}:$HOME/
      server_dir
      :$DB2DIR/lib
  4. Edit the .cshrc or .profile to include the complete set of shell commands. Save the file and either log out and log in again or run the source command.
    Using a Bourne shell:
    $ source .profile
    Using a C shell:
    $ source .cshrc
  5. If the DB2 database resides on the same machine on which the Data Integration Service, PowerCenter Integration Service, or PowerCenter Repository Service process runs, configure the DB2 instance as a remote instance.
    Run the following command to verify if there is a remote entry for the database:
    DB2 LIST DATABASE DIRECTORY
    The command lists all the databases that the DB2 client can access and their configuration properties. If this command lists an entry for “Directory entry type” of “Remote,” skip to step 6.
    If the database is not configured as remote, run the following command to verify whether a TCP/IP node is cataloged for the host:
    DB2 LIST NODE DIRECTORY
    If the node name is empty, you can create one when you set up a remote database. Use the following command to set up a remote database and, if needed, create a node:
    db2 CATALOG TCPIP NODE <nodename> REMOTE <hostname_or_address> SERVER <port number>
    Run the following command to catalog the database:
    db2 CATALOG DATABASE <dbname> as <dbalias> at NODE <nodename>
    For more information about these commands, see the database documentation.
  6. Verify that you can connect to the DB2 database. Run the DB2 Command Line Processor and run the command:
    CONNECT TO <dbalias> USER <username> USING <password>
    If the connection is successful, clean up with the
    CONNECT RESET
    or
    TERMINATE
    command.