Table of Contents

Search

  1. Preface
  2. Installing Informatica MDM - Relate 360
  3. Configuring Relate 360
  4. Configuring Security
  5. Setting Up the Environment to Process Streaming Data
  6. Configuring Distributed Search
  7. Packaging and Deploying the RESTful Web Services
  8. Troubleshooting

Installation and Configuration Guide

Installation and Configuration Guide

Configuring the Match Rule Set

Configuring the Match Rule Set

You can define one or more match rule sets in a matching rules file. A match rule set definition includes an index, one or more searches, and one or more matching rules. You can define a match rule set within the MDMBDRMMatchRulesSet section.
To define a match rule set, add the following parameters to the MDMBDRMMatchRuleSet section within the MDMBDRMMatchRulesSet section:
Id
Identifier for the match rule set.
Name
Name for the match rule set.
Population
Optional. Name of the population to use for the match process. If you want to include multiple populations for the match process, create additional match rule sets for the populations that you want to include.
Use the population file name without the extension as the parameter value. By default, the MapReduce jobs use the population that you specify in the configuration file.
The following sample shows the match rule set definitions for the Arabic and Chinese populations:
<MDMBDRMMatchRulesSet>
   <MDMBDRMMatchRuleSet Id="00" Name="WI04NAR" Population="arabic_r">
      <IndexingConfiguration>
         <indexFieldName>IDS_name,IDS_alias1,IDS_alias2</indexFieldName>
         <indexType>FUZZY</indexType>
         <keyField>Person_Name</keyField>
         <keyLevel>Extended</keyLevel>
         <AdditionalControl>NAMEFORMAT=L</AdditionalControl>
      </IndexingConfiguration>
      <SearchConfiguration>
         <searchType>WI04NARABIC</searchType>
         <searchFieldName>IDS_name,IDS_alias1,IDS_alias2</searchFieldName>
         <keyField>Person_Name</keyField>
         <searchLevel>Exhaustive</searchLevel>
         <AdditionalControl>NAMEFORMAT=L</AdditionalControl>
      </SearchConfiguration>
      <LWMMatchConfiguration>
         <Purpose>Person_Name</Purpose>
         <MatchLevel>Typical</MatchLevel>
         <Threshold>85</Threshold>
         <MatchField>
            <MField name="Person_Name" type="Fuzzy">fullName</MField>
         </MatchField>
      </LWMMatchConfiguration>
      <MatchRuleSet>
         <MatchConfiguration MatchRuleID="WI04NAR" AutoMergeInd="yes">
            <Purpose>Person_Name</Purpose>
            <MatchLevel>Typical</MatchLevel>
            <Threshold>70</Threshold>
            <MatchField>
               <MField name="Person_Name" type="Fuzzy">IDS_name</MField>
               <MField name="Person_Name" type="Fuzzy">IDS_alias1</MField>
            </MatchField>
            <AdditionalControl />
         </MatchConfiguration>
      </MatchRuleSet>
   </MDMBDRMMatchRuleSet>
   <MDMBDRMMatchRuleSet Id="01" Name="WI04NCH" Population="chinese_r">
      <IndexingConfiguration>
         <indexFieldName>IDS_name</indexFieldName>
         <indexType>User</indexType>
         <PARTITION_COLUMN_NAME length="5" part_of_rowkey="YES">Zip</PARTITION_COLUMN_NAME>
      </IndexingConfiguration>
      <SearchConfiguration>
         <searchType>WI04NCH</searchType>
         <searchFieldName>IDS_name</searchFieldName>
      </SearchConfiguration>
      <MatchRuleSet>
         <MatchConfiguration MatchRuleID="WI04NCH" AutoMergeInd="yes">
            <MatchField>
               <MField name="Person_Name" type="Exact">IDS_name</MField>
               <MField name="Person_Name" type="Exact">IDS_alias1</MField>
            </MatchField>
         </MatchConfiguration>
      </MatchRuleSet>
   </MDMBDRMMatchRuleSet>
</MDMBDRMMatchRulesSet>


Updated June 27, 2019


Explore Informatica Network