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 a Sybase ASE 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 to the Data Integration Service, PowerCenter Integration Service, or PowerCenter Repository Service process, log in to the machine as a user who can start the server process.
  2. Set the SYBASE and PATH environment variables.
    SYBASE
    . Set the variable to the Sybase Open Client installation directory. For example if the client is installed in the /usr/sybase directory:
    Using a Bourne shell:
    $ SYBASE=/usr/sybase; export SYBASE
    Using a C shell:
    $ setenv SYBASE /usr/sybase
    PATH
    . To run the Sybase command line programs, set the variable to include the Sybase OCS bin directory.
    Using a Bourne shell:
    $ PATH=${PATH}:/usr/sybase/OCS-15_0/bin; export PATH
    Using a C shell:
    $ setenv PATH ${PATH}:/usr/sybase/OCS-15_0/bin
  3. Set the shared library environment variable.
    The Sybase Open 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 installation directory of the Informatica services
    (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
      :$SYBASE/OCS-15_0/lib;$SYBASE/OCS-15_0/lib3p;$SYBASE/OCS-15_0/lib3p64; export LD_LIBRARY_PATH
    • Using a C shell:
      $ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/
      server_dir
      :$SYBASE/OCS-15_0/lib;$SYBASE/OCS-15_0/lib3p;$SYBASE/OCS-15_0/lib3p64;
    For AIX
    • Using a Bourne shell:
      $ LIBPATH=${LIBPATH}:$HOME/
      server_dir
      :$SYBASE/OCS-15_0/lib;$SYBASE/OCS-15_0/lib3p;$SYBASE/OCS-15_0/lib3p64; export LIBPATH
    • Using a C shell:
      $ setenv LIBPATH ${LIBPATH}:$HOME/
      server_dir
      :$SYBASE/OCS-15_0/lib;$SYBASE/OCS-15_0/lib3p;$SYBASE/OCS-15_0/lib3p64;
  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. Verify the Sybase ASE server name in the Sybase interfaces file stored in the $SYBASE directory.
  6. Verify that you can connect to the Sybase ASE database.
    To connect to the Sybase ASE database, launch ISQL and enter the connectivity information. If you fail to connect to the database, verify that you correctly entered all of the connectivity information.
    User names and database names are case sensitive.