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

MANAGECLUSTER Operation

MANAGECLUSTER Operation

The MANAGECLUSTER operation indicates to read the input records, remove the input records from their respective clusters, and move the records to the specified cluster or to a new cluster. If you do not specify the cluster number in the input file, the MANAGECLUSTER operation indicates to create a cluster and move the specified records to the created cluster.
Run the
run_client.sh
script located in the following directory to perform the MANAGECLUSTER 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=MANAGECLUSTER --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
MANAGECLUSTER
Type of operation that you want to perform. Specify MANAGECLUSTER.
--input
input_file_name
Absolute path and name of the input JSON file that contains the input data.
--outputfile
output_file_name
Optional. Absolute path and name of the output JSON file to which you want to load the processed data.
For example:
run_client.sh --config=/usr/local/tree/configuration.xml --operation=MANAGECLUSTER --input=/usr/local/tree/input.json --rule=usr/local/conf/matching_rules.xml --outputfile=/usr/local/tree/output.json
The following input data contains a record that you want to add it to the specified cluster number:
{ "clusterNumber":"12b1ea9f-4f5c-4168-828e-1b03edef0c6a ", "members":[ { "LMT_SOURCE_NAME":"AML", "PK":"0000300003" } ], "resultCount":0, "messages":{ } }
The following sample output shows a record that the MANAGECLUSTER operation submits for processing:
{ "clusterNumber": "12b1ea9f-4f5c-4168-828e-1b03edef0c6a ", "members": [ { "LMT_SOURCE_NAME": "AML", "PK": "0000300003" } ], "resultCount": 1, "messages": { "Message.1": "Record submitted for Processing" } }

0 COMMENTS

We’d like to hear from you!