Table of Contents

Search

  1. Preface
  2. Introduction to Informatica MDM - Relate 360
  3. Linking Batch Data
  4. Tokenizing Batch Data
  5. Processing Streaming Data
  6. Creating Relationship Graph
  7. Loading Linked and Consolidated Data into Hive
  8. Searching Data
  9. Monitoring the Batch Jobs
  10. Troubleshooting
  11. Glossary

User Guide

User Guide

Preferred Record Search Operation

Preferred Record Search Operation

The Preferred Record Search operation searches the primary key table in the repository and retrieves the records that match the input data based on the rules in the matching rules file. The Preferred Record Search operation then uses the cluster numbers of the matching records to return the corresponding preferred records from the preferred record table.
Before you run the Preferred Record Search operation, run the Get Multisearch Layout operation to get the search layout details in the JSON format for the matching rules file. Based on the search layout details, you can configure the input parameters for the Preferred Record Search operation.
Ensure that you consolidate the linked data before you run the Preferred Record Search operation.
Run the
run_client.sh
script located in the following directory to perform the Preferred Record Search operation:
/usr/local/mdmbdrm-<Version Number>
Use the following command to run the
run_client.sh
script:
run_client.sh --config=configuration_file_name --rule=matching_rules_file_name --operation=PREFERREDRECORDSEARCH --input=input_file_name [--outputfile=output_file_name]
The following table describes the options and arguments that you can specify to run the
run_client.sh
script:
Option
Argument
Description
--config
configuration_file_name
Absolute path and file name of the configuration file that you create.
--rule
matching_rules_file_name
Absolute path and file name of the matching rules file that you create.
--operation
PREFERREDRECORDSEARCH
Type of operation that you want to perform. Specify PREFERREDRECORDSEARCH as the value.
--input
input_file_name
Absolute path and name of the input JSON file that you configure based on the search layout details.
--outputfile
output_file_name
Optional. Absolute path and name of the output JSON file to which you want to load the search results.
For example, the following command identifies the matching records for a single search record:
run_client.sh --config=/usr/local/tree/configuration.xml --rule=/usr/local/conf/matching_rules.xml --operation=PREFERREDRECORDSEARCH --input=/usr/local/tree/input.json --outputfile=/usr/local/tree/output.json
The following sample response shows the preferred record for the input record:
{ "searchType": "Employee", "resultlimit": 200, "scoreThreshold": 0, "ignoreMatch": false, "searchinput": { "NAME": "John Smith" }, "searchlayout": {}, "searchResults": [ { "COMPANY": "INFA", "MatchRuleID": "match.rule", "NAME": "John Smith", "AGE": "30", "ROW_RULE": "DEFAULT_RULE_MAX_COLUMN_VALUES", "COLUMN_RULE": "NONE", "ADDRESS": "Bagmane TechPark", "score": "100", "DOJ": "2013", "match_decision": "ACCEPT", "PHONE": "08040201000", "LMT_DIRTY_IND": "0", "CLUSTERNUMBER": "e83354b3-1558-4ab8-90ab-9c8ff03c6b28", "SOURCE": "Salesforce", "SALARY": "10000", "ID": "9", "PINCODE": "560103", "CITY": "Bangalore", "MatchedIndex": "00", "LMT_CREATE_DATE": "20180622132346", "LMT_SOURCE_NAME": "Salesforce" } ], "searchToken": -1, "pageLimit": 10, "pageOffset": 0, "totalCount": 0, "prSearchType": "Optimal", "debug": false, "resultCount": 1, "messages": { "Response Time": "345 ms" } }

0 COMMENTS

We’d like to hear from you!