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
  • MDM Registry Edition 10.5 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Installing MDM Registry Edition
  4. Post-Installation Tasks
  5. Troubleshooting
  6. Upgrading MDM Registry Edition
  7. Uninstalling MDM Registry Edition

Installation and Configuration Guide

Installation and Configuration Guide

Back Next

Step 4. Define an ODBC Data Source

Step 4. Define an ODBC Data Source

Define an ODBC data source on the Search Server to connect to IBM DB2 UDB. The
MDM Registry Edition
 components access the database through ODBC. You must create ODBC data sources for each database that you plan to access.
  1. Open the
    odbc.ini
     file that you can find in the
    <MDM Registry Edition Installation Directory>\bin
     directory on Windows or
    <MDM Registry Edition Installation Directory>/bin
     on UNIX, and add or update the following database entries: 
    [<Service Name>]
DataSourceName = <ODBC DSN>
driver = <ODBC Driver>
server = <Native Database Service>
[connect_attributes = <Keyword1=Value1;Keyword2=Value2;...>]
[connect_string_udb = CONNECT TO <Database Name>]
[connect_attr_only = <Text1>]
    Configure the following parameters:
    Service Name
    Service name that
    MDM Registry Edition
     uses to refer to the database service.
    ODBC DSN
    Data Source Name. If you do not specify any value, it defaults to the service name.
    ODBC Driver
    Name of the ODBC driver. The driver name does not include the directory path. Enter one of the following values:
    • db2cli
       on Windows
    • db2
       on UNIX
    • libdb2.a(shr_64.o)
       on 64-bit AIX environments
    Native Database Service
    Name of the database alias.
    Keywords
    List of connection string keywords that
    MDM Registry Edition
     uses to generate a connection string that establishes a connection with IBM DB2 UDB.
    The format uses the following values:
    • Keywords
      . Optional. Connection string keywords that your ODBC driver supports. If you enable the
      connect_attr_only
       parameter, the specified values override the database source definitions and creates the connection string based only on the specified values. If you do not include the
      connect_attr_only
       parameter,
      MDM Registry Edition
       uses the specified values and the database source definitions to create the connection string.
    • Database Name
      . Optional. The database name which authenticates the connection to IBM DB2 UDB.
    • Text1
      . Optional. Indicates whether to use only the connection string keywords or the connection string keywords along with other data source definitions to create the connection string. Enter any text, such as
      Yes
      , to use only the keywords specified in the
      connection_attributes
       parameter to create the connection string. If you want to use the specified keywords with other database source definitions, do not add the
      connect_attr_only
       parameter to the
      odbc.ini
       file.
    The following sample configuration indicates to use only the specified connection string keywords to create the connection string: 
    [KRBTEST]
driver = /opt/ibm/db2/V11.1/lib64/libdb2o.so
server = KRBTEST
connect_attributes = DSN=DBKRB;
connect_string_udb = CONNECT TO DBKRB;
connect_attr_only = Yes
    For the preceding sample configuration, you get the following connection string which enables connection to IBM DB2 UDB using Kerberos authentication:
    DSN=DBKRB
    You need not specify User ID or Password in the
    connect_attributes
     parameter as
    MDM Registry Edition
     uses the predefined Kerberos authorization.
    A sample configuration file,
    odbc.ini.ori
    , is located in the following directory:
    • On Windows:
      <MDM Registry Edition Installation Directory>\bin
    • On UNIX:
      <MDM Registry Edition Installation Directory>/bin
    If you use multiple databases, add the database entries for each database. For example: 
    [srcDBcli] 
driver = db2cli 
server = (local) 
DataSourceName = srcDBcli

[tgtDBcli] 
driver = db2cli 
server = (local) 
DataSourceName = tgtDBcli
  2. Open the ODBC Data Source Administrator by performing the following tasks:
    1. From the Windows Control Panel, click
      Administrative Tools
      .
    2. In the
      Administrative Tools
       dialog box, double-click
      Data Sources (ODBC)
      .
  3. On the
    User DNS
     tab or
    Service DNS
     tab, click
    Add
    .
  4. Select
    IBM DB2 ODBC DRIVER
    , and click
    Finish
    .
  5. Follow the instructions in the Wizard, and ensure that you enter the following values:
    • Specify a data source name. Ensure that the data source name matches the data source name that you specify in the
      odbc.ini
       file.
    • Specify a default database.
0 COMMENTS
We’d like to hear from you!