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
  • Multidomain MDM 10.3 HotFix 2
  • All Products

Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 9.7.1

Upgrading from Version 9.7.1

Back Next

Register the Operational Reference Stores

Register the Operational Reference Stores

To register the Operational Reference Stores, use the Hub Console.
  1. Start the
    Databases
     tool under the
    Configuration
     workbench.
  2. Click
    Write Lock
    Acquire Lock
    .
  3. Click
    Register database
    .
    The
    Informatica MDM Hub Connection Wizard
     appears and prompts you to select the database type.
  4. Select Microsoft SQL Server, Oracle, or IBM DB2, and click
    Next
    .
  5. In Microsoft SQL Server, configure connection properties for the database.
    1. In the Connection Properties page, specify the connection properties, and then click
      Next
      .
      The following table lists and describes the connection properties:
      Property
      Description
      Database Display Name
      Name for the Operational Reference Store that must appear in the Hub Console.
      Machine Identifier
      Prefix given to keys to uniquely identify records from the Hub Store instance.
      Database hostname
      IP address or name of the server that hosts the Microsoft SQL Server database.
      Port
      Port of the Microsoft SQL Server database. The default is 1433.
      Schema Name
      Name of the Operational Reference Store.
      Password
      Password associated with the user name for the Operational Reference Store.
      Dynamic Data Masking
       host
      IP address or name of the server that hosts
      Dynamic Data Masking
      . Leave empty if you do not use
      Dynamic Data Masking
      .
      DDM connection URL
      Optional. URL for the
      Dynamic Data Masking
       server. Leave empty if you do not use
      Dynamic Data Masking
      .
    2. In the Connection Properties page, specify the connection properties, and then click
      Next
      .
    3. Review the summary, and specify additional connection properties.
      The following table lists additional connection properties that you can configure:
      Property
      Description
      Connection URL
      Connect URL. The Connection Wizard generates the connect URL by default.
      Create datasource after registration
      Select to create the datasource on the application server after registration.
  6. In Oracle environments, configure connection properties for the database.
    1. Select an Oracle connection method, and click
      Next
      .
      The following table describes the Oracle connection methods that you can select:
      Connection Method
      Description
      Service
      Connect to Oracle by using the service name.
      SID
      Connect to Oracle by using the Oracle System ID.
      For more information about SERVICE and SID names, see the Oracle documentation.
      The
      Connection Properties
       page appears.
    2. Specify the connection properties for the connection type that you select, and click
      Next
      .
      The following table lists and describes the connection properties:
      Property
      Description
      Database Display Name
      Name for the Operational Reference Store that must appear in the Hub Console.
      Machine Identifier
      Prefix given to keys to uniquely identify records from the Hub Store instance.
      Database hostname
      IP address or name of the server that hosts the Oracle database.
      SID
      Oracle System Identifier that refers to the instance of the Oracle database running on the server. The
      SID
       field appears if you selected the
      SID
       connection type.
      Service
      Name of the Oracle SERVICE used to connect to the Oracle database. The
      Service
       field appears if the you selected the
      Service
       connection type.
      Port
      The TCP port of the Oracle listener running on the Oracle database server. The default is
      1521
      .
      Oracle TNS Name
      Name by which the database is known on your network as defined in the
      TNSNAMES.ORA
       file of the application server.
      For example:
      mydatabase.mycompany.com
      .
      You set the Oracle TNS name when you install the Oracle database. For more information about the Oracle TNS name, see the Oracle documentation.
      Schema Name
      Name of the Operational Reference Store.
      User name
      User name for the Operational Reference Store. By default, this is the user name that you specify in the script that you use to create the Operational Reference Store. This user owns all of the Operational Reference Store database objects in the Hub Store.
      If a proxy user is configured for the Operational Reference Store, then you can specify the proxy user instead.
      Password
      Password associated with the user name for the Operational Reference Store.
      For Oracle, the password is not case sensitive.
      By default, this is the password that you specify when you create the Operational Reference Store.
      If a proxy user is configured for the Operational Reference Store, then you specify the password for the proxy user instead.
      Dynamic Data Masking
       host
      IP address or name of the server that hosts
      Dynamic Data Masking
      . Leave empty if you do not use
      Dynamic Data Masking
      .
      DDM connection URL
      Optional. URL for the
      Dynamic Data Masking
       server. Leave empty if you do not use
      Dynamic Data Masking
      .
      The
      Schema Name
       and the
      User Name
       are both the names of the Operational Reference Store that you specified when you created the Operational Reference Store. If you need this information, consult your database administrator.
      The
      Summary
       page appears.
    3. Review the summary, and specify additional connection properties.
      The following table lists additional connection properties that you can configure:
      Property
      Description
      Connection URL
      Connect URL. The Connection Wizard generates the connect URL by default. The following list shows the format of the connect URL for the Oracle connection types:
      Service connection type
      jdbc:oracle:thin:@//database_host:port/service_name
      SID connection type
      jdbc:oracle:thin:@//database_host:port:sid
      For a service connection type only, you have the option to customize and later test a different connection URL.
      Create datasource after registration
      Select to create the datasource on the application server after registration.
      If you do not select the option, you must manually configure the data source.
    4. For a service connection type, if you want to change the default URL, click the
      Edit
       button, specify the URL, and then click
      OK
      .
  7. In IBM DB2 environments, configure connection properties for the database.
    1. Specify the connection properties, and click
      Next
      .
      The following table lists and describes the connection properties:
      Property
      Description
      Database Display Name
      Name for the Operational Reference Store that must appear in the Hub Console.
      Machine Identifier
      Prefix given to keys to uniquely identify records from the Hub Store instance.
      Database server name
      IP address or name of the server that hosts the IBM DB2 database.
      Database name
      Name of the database that you create.
      Database hostname
      IP address or name of the server that hosts the IBM DB2 database.
      Schema Name
      Name of the Operational Reference Store.
      User name
      User name for the Operational Reference Store. By default, this is the user name that you specify in the script that you use to create the Operational Reference Store. This user owns all the Operational Reference Store database objects in the Hub Store.
      If a proxy user is configured for the Operational Reference Store, then you can specify the proxy user instead.
      Password
      Password associated with the user name for the Operational Reference Store.
      For IBM DB2, the password is case sensitive.
      By default, this is the password that you specify when you create the Operational Reference Store.
      If a proxy user is configured for the Operational Reference Store, then you specify the password for the proxy user instead.
      Dynamic Data Masking
       host
      IP address or name of the server that hosts
      Dynamic Data Masking
      . Leave empty if you do not use
      Dynamic Data Masking
      .
      DDM connection URL
      Optional. URL for the
      Dynamic Data Masking
       server. Leave empty if you do not use
      Dynamic Data Masking
      .
      The
      Schema Name
       and the
      User Name
       are both the names of the Operational Reference Store that you specified when you created the Operational Reference Store. If you need this information, consult your database administrator.
      The
      Summary
       page appears.
    2. Review the summary, and specify additional connection properties.
      The following table lists additional connection properties that you can configure:
      Property
      Description
      Connection URL
      Connect URL. The Connection Wizard generates the connect URL by default. The following example shows the format of the connect URL: 
      jdbc:db2://database_host:port/db_name
      Create datasource after registration
      Select to create the datasource on the application server after registration.
      If you do not select the option, you must manually configure the data source.
  8. Click
    Finish
    .
    The
    Registering Database
     dialog box appears.
  9. Click
    OK
    .
    The
    Application Server Login
     dialog box appears.
  10. Enter the WebSphere administrative user name and password.
  11. Click
    OK
    .
    The MDM Hub registers the ORS.
  12. Restart the application server.
  13. Select the Operational Reference Store that you registered, and click the
    Test database connection
     button to test the database settings.
    The Test Database dialog box displays the result of the database connection test.
  14. Click
    OK
    The ORS is registered, and the connection to the database is tested.
0 COMMENTS
We’d like to hear from you!