Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Editing Operational Reference Store Properties

Editing Operational Reference Store Properties

You can change the properties for a registered Operational Reference Store.
  1. Start the
    Databases
    tool.
  2. Acquire a write lock.
  3. Select the Operational Reference Store that you want to configure.
    The Databases tool displays the database properties for the selected Operational Reference Store.
    The following table describes the database properties:
    Property
    Description
    Database Type
    Type of database such as Oracle, or Microsoft SQL Server.
    Database ID
    Identification for the Operational Reference Store. The MDM Hub uses the database ID in SIF requests. The database ID lookup is case-sensitive.
    The database ID for Oracle uses the following format:
    • If the Oracle connection type is SID, the format is
      hostname-sid-databasename
      .
    • If the Oracle connection type is Service, the format is
      hostname-sid-databasename
      .
    The database ID for Microsoft SQL Server uses the following format:
    hostname-databasename
    When you register an Operational Reference Store, the MDM Hub normalizes the host, server, and database names.
    The MDM Hub converts the host name to lowercase, and the database name to uppercase, which is the standard for database objects such as schemas and tables.
    JNDI Datasource Name
    The data source JNDI name for the Operational Reference Store that you select. This is the JNDI name that the MDM Hub configures for the JDBC connection on the application server.
    The JNDI data source name for Oracle uses the following format:
    • If the Oracle connection type is SID, the format is
      jdbc/siperian-hostname-sid-databasename-ds
      .
    • If the Oracle connection type is Service, the format is
      jdbc/siperian-servicename-databasename-ds
      .
    The JNDI data source for Microsoft SQL Server uses the following format:
    jdbc/siperian-hostname-databasename-ds
    Machine Identifier
    Prefix assigned to keys to uniquely identify records from the Hub Store instance.
    GETLIST Limit (records)
    Limit for the number of records returned through SIF search requests such as searchQuery, searchMatch, and getLookupValues. Default is 200 and the maximum value is 5,999.
    Production Mode
    Specifies whether the Operational Reference Store is in production mode or normal mode.
    If disabled, authorized users can edit metadata for the Operational Reference Store in the Hub Console. Default is disabled.
    If enabled, users cannot edit the metadata for the Operational Reference Store. If a user attempts to acquire a write lock on an Operational Reference Store in production mode, the
    Hub Console
    displays a message explaining that the lock cannot be obtained.
    Only an MDM Hub administrator user can enable or disable the production mode for an Operational Reference Store.
    Transition Mode
    Specifies whether the Operational Reference Store is running in transition mode. Transition mode is available if you enable production mode for the Operational Reference Store.
    If enabled, users can perform the promote actions of the
    Repository Manager
    .
    If disabled, users cannot perform the promote actions of the
    Repository Manager
    .
    Batch API Interoperability
    Specifies whether the MDM Hub can use row-level locking for the Operational Reference Store for concurrently executing, asynchronous SIF and batch operations.
    If enabled, row-level locking is available for asynchronous SIF and batch operations.
    If disabled, row-level locking is unavailable.
    ZDT Enabled
    Specifies whether the Operational Reference Store is running in Zero Downtime (ZDT) mode.
    If enabled, the Operational Reference Store runs in ZDT mode.
    If disabled, the Operational Reference Store does not runs in ZDT mode.
  4. To change a property, click the
    Edit
    button next to it, and edit the property.
  5. Click the
    Save
    button to save the changes.
    If you enable production mode for an Operational Reference Store, the Databases tool displays a lock icon next to the Operational Reference Store in the list.

0 COMMENTS

We’d like to hear from you!