Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Common Content for Data Catalog 10.5.3
  • All Products

Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service REST API
  10. Data Integration Service Applications
  11. Data Privacy Management Service
  12. Enterprise Data Preparation Service
  13. Interactive Data Preparation Service
  14. Informatica Cluster Service
  15. Mass Ingestion Service
  16. Metadata Access Service
  17. Metadata Manager Service
  18. Model Repository Service
  19. PowerCenter Integration Service
  20. PowerCenter Integration Service Architecture
  21. High Availability for the PowerCenter Integration Service
  22. PowerCenter Repository Service
  23. PowerCenter Repository Management
  24. PowerExchange Listener Service
  25. PowerExchange Logger Service
  26. SAP BW Service
  27. Search Service
  28. System Services
  29. Test Data Manager Service
  30. Test Data Warehouse Service
  31. Web Services Hub
  32. Application Service Upgrade
  33. Appendix A: Application Service Databases
  34. Appendix B: Connecting to Databases from Windows
  35. Appendix C: Connecting to Databases from UNIX or Linux
  36. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Application Service Guide

Application Service Guide

Back Next

Connecting to an ODBC Data Source

Connecting to an ODBC Data Source

Install and configure native client software on the machine where the Data Integration Service, PowerCenter Integration Service, and PowerCenter Repository Service run. Also install and configure any underlying client access software required by the ODBC driver. To ensure compatibility between Informatica and the databases, use the appropriate database client libraries.
The Informatica installation includes DataDirect ODBC drivers. If the odbc.ini file contains connections that use earlier versions of the ODBC driver, update the connection information to use the new drivers. Use the System DSN to specify an ODBC data source on Windows.
  1. On the machine where the application service runs, log in as a user who can start a service process.
  2. Set the ODBCHOME and PATH environment variables.
    ODBCHOME
    . Set to the DataDirect ODBC installation directory. For example, if the install directory is
    /export/home/Informatica/10.0.0/ODBC7.1
    .
    Using a Bourne shell: 
    $ ODBCHOME=/export/home/Informatica/10.0.0/ODBC7.1; export ODBCHOME
    Using a C shell: 
    $ setenv ODBCHOME /export/home/Informatica/10.0.0/ODBC7.1
    PATH
    . To run the ODBC command line programs, like
    ddtestlib
    , set the variable to include the odbc bin directory.
    Using a Bourne shell: 
    $ PATH=${PATH}:$ODBCHOME/bin; export PATH
    Using a C shell: 
    $ setenv PATH ${PATH}:$ODBCHOME/bin
    Run the
    ddtestlib
     utility to verify that the DataDirect ODBC driver manager can load the driver files.
  3. Set the shared library environment variable.
    The ODBC software contains a number of shared library components that the 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
    Linux
    LD_LIBRARY_PATH
    AIX
    LIBPATH
    For example, use the following syntax for Linux:
    • Using a Bourne shell: 
      $ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/
      server_dir
      :$ODBCHOME/lib; export LD_LIBRARY_PATH
    • Using a C shell: 
      $ setenv LD_LIBRARY_PATH $HOME/server_dir:$ODBCHOME:${LD_LIBRARY_PATH}
    For AIX
    • Using a Bourne shell: 
      $ LIBPATH=${LIBPATH}:$HOME/
      server_dir
      :$ODBCHOME/lib; export LIBPATH
    • Using a C shell: 
      $ setenv LIBPATH ${LIBPATH}:$HOME/
      server_dir
      :$ODBCHOME/lib
  4. Edit the existing odbc.ini file or copy the odbc.ini file to the home directory and edit it.
    This file exists in $ODBCHOME directory. 
    $ cp $ODBCHOME/odbc.ini $HOME/.odbc.ini
    Add an entry for the ODBC data source under the section [ODBC Data Sources] and configure the data source.
    For example: 
    MY_MSSQLSERVER_ODBC_SOURCE=<Driver name or data source description>
[MY_SQLSERVER_ODBC_SOURCE]
Driver=<path to ODBC drivers>
Description=DataDirect 8.0 SQL Server Wire Protocol
Database=<SQLServer_database_name>
LogonID=<username>
Password=<password>
Address=<TCP/IP address>,<port number>
QuoteId=No
AnsiNPW=No
ApplicationsUsingThreads=1
    This file might already exist if you have configured one or more ODBC data sources.
  5. Verify that the last entry in the odbc.ini is InstallDir and set it to the odbc installation directory.
    For example: 
    InstallDir=/export/home/Informatica/10.0.0/ODBC7.1
  6. If you use the odbc.ini file in the home directory, set the ODBCINI environment variable.
    Using a Bourne shell: 
    $ ODBCINI=/$HOME/.odbc.ini; export ODBCINI
    Using a C shell: 
    $ setenv ODBCINI $HOME/.odbc.ini
  7. 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
  8. Use the
    ddtestlib
     utility to verify that the DataDirect ODBC driver manager can load the driver file you specified for the data source in the odbc.ini file.
    For example, if you have the driver entry: 
    Driver = /export/home/Informatica/10.0.0/ODBC7.1/lib/DWxxxxnn.so
    run the following command: 
    ddtestlib /export/home/Informatica/10.0.0/ODBC7.1/lib/DWxxxxnn.so
  9. Install and configure any underlying client access software needed by the ODBC driver.
    While some ODBC drivers are self-contained and have all information inside the .odbc.ini file, most are not. For example, if you want to use an ODBC driver to access Sybase IQ, you must install the Sybase IQ network client software and set the appropriate environment variables.
    To use the Informatica ODBC drivers (DWxxxxnn.so), manually set the PATH and shared library path environment variables. Alternatively, run the odbc.sh or odbc.csh script in the $ODBCHOME folder. This script will set the required PATH and shared library path environment variables for the ODBC drivers provided by Informatica.
0 COMMENTS
We’d like to hear from you!