Table of Contents


  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

Using Multiple Populations Within a Single Base Object

Using Multiple Populations Within a Single Base Object

You can use multiple populations within a single base object in the MDM Hub.
This is useful if data in a base object comes from different populations. For example, 70% of the records come from the United States and 30% come from China. Populations can vary on a record-by-record basis.
To use multiple populations within a base object, perform the following steps:
  1. Contact Informatica Global Customer Support to get the applicable
    files for your implementation, along with instructions for enabling the population.
  2. For each population that you want to use, enable it in the C_REPOS_SSA_POPULATION metadata table.
  3. Copy the applicable population files to the following location:
    On UNIX.
    <MDM Hub installation directory>/hub/cleanse/
    On Windows.
    <MDM Hub installation directory>\cleanse\resources\match
  4. Restart the application server.
  5. In the Schema Manager, add a VARCHAR column named SIP_POP to the base object that contains the population to use for each record.
    The width of the VARCHAR column must fit the largest population name in use. A width of 30 is sufficient for most implementations.
  6. Configure the match column as an exact match column with the name of SIP_POP.
  7. For each record in the base object that uses a population that is not the default, in the SIP_POP column enter the name of the population to use instead.
    You can specify values for the SIP_POP column in one of the following ways:
    • Add the UTF-8 data in the landing tables.
    • Use cleanse functions that calculate the values during the stage process.
    • Invoke SIF requests from external applications.
    • Edit the column values manually through the Data Manager tool.
    Data in the SIP_POP column is not case sensitive, but the MDM Hub processes invalid values, such as NULL values or empty strings, using the default population.
  8. Run the Generate Match Tokens process on the base object to update the match key table.
  9. Run the match process on the base object.
    The match process compares only records that share the same population. For example, the match process compares Chinese records with Chinese records, and American records with American records.


We’d like to hear from you!