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

Configuring Match Settings for Non-US Populations

Configuring Match Settings for Non-US Populations

If the MDM Hub implementation uses a non-US population, configure the population set and enable encoding for match processing. A population set encapsulates intelligence about name, address, and other identification information that is typical for a particular population. For more information about population sets, see Population Sets.
The MDM Hub includes a
file and a
file. The
file contains a population for demonstration purposes only and must not be used for actual match rules. In your MDM Hub implementation, use the
population file for which you purchased a license. If you do not have a population file, contact Informatica Global Customer Support to get a population file that is appropriate for your implementation.
Decide on a population set based on the following considerations:
  • If the data is exclusively from one country and Informatica provides a population set for that country, then use that population.
  • If the data is mostly from one country with small amounts of mixed data from one or more countries, use the majority population.
  • If the data is from different countries with large amounts of mixed data, consider whether it is meaningful to match across such a disparate set of data. If so, then use the
For more information about enabling a match population, see the
Multidomain MDM Installation Guide


We’d like to hear from you!