Data Director Implementation Guide

10.4

Back Next

Step 5.2. Configure Extended Search

Extended Search uses the searchMatch API to request fuzzy searches through the data.

You need to ensure that all necessary match columns have been created. No extra configuration is required in an IDD application to enable the fuzzy search. IDD will automatically map the search criteria supplied by the IDD application user to the available match-enabled columns, and then execute the search.

Before testing the Extended Search configuration, verify that the data has been properly tokenized, then test the fuzzy search facilities by creating the search queries to include the subject area attributes that have underlying match-enabled columns.

For more information, refer to "Configuring the Match Process" in the

Multidomain MDM Configuration Guide

or Hub Console online help, as well as the description of the searchMatch API in the

Multidomain MDM Services Integration Framework Guide

or Javadoc.

Extended Search uses the

searchMatch

API with matchType=NONE. In the default configuration, all possible match columns get generated on each searchMatch request. IDD can be configured to generate only specific match columns. On the Search tab in the subject area dialog box, you can specify the specific set of match columns that is to be generated.

By default, in this mode of searchMatch, the search level defaults to Narrow. This is the most restrictive level, but it can be overridden by configuring the following setting in cmxcleanse.properties:

cmx.server.match.searcher_search_level=<level>

where <level> is one of the following settings: Narrow, Typical, Exhaustive, or Extreme. For more information about search levels in match rule set properties, see "Configuring the Match Process" in the

Rename Saved Search

Table of Contents

Data Director Implementation Guide

Data Director Implementation Guide

Step 5.2. Configure Extended Search

Step 5.2. Configure Extended Search