Services Integration Framework Guide

10.4

Back Next

ExecuteBatchMatchAnalyze

An ExecuteBatchMatchAnalyze request conducts a search to gather match statistics, but does not perform the match process. If areas of data with the potential for huge match requirements are discovered, the MDM Hub moves the records to a hold status, which allows a data steward to review the data manually before proceeding with the match process.

Request Parameters

The ExecuteBatchMatchAnalyze request contains the following parameters:

TableName: Name of the base object table.
validateTableName: Optional. Name of the table that contains the row ID values to validate. Default is null.

Response Fields

The ExecuteBatchMatchAnalyze request returns the following fields:

InteractionId: An identifier for the request.
Message: A brief message about the status of the request.
RetCode: Return code for the interaction. The RetCode field uses the following return codes:
0. Indicates a successful transaction.
-21014. Indicates that the base object is empty or no records match the request.

Usage Example

The following example runs a match analysis batch job on a base object table:

SiperianClient sipClient = SiperianClient.newSiperianClient(
    new File(context.getTestPTTStartDir() + "siperian-client.properties")
    );
ExecuteBatchMatchAnalyzeRequest l_req = new ExecuteBatchMatchAnalyzeRequest();
l_req.setTableName("<BO_TABLE_NAME>");
l_req.setValidateTableName("<TABLE_NAME_CONTAINING_ROWID_TO_VALIDATE>");
ExecuteBatchMatchAnalyzeResponse l_res = (ExecuteBatchMatchAnalyzeResponse)
    sipClient.process( l_req );
System.out.println(l_res.getRetCode());

Rename Saved Search

Table of Contents

Services Integration Framework Guide

Services Integration Framework Guide

ExecuteBatchMatchAnalyze

ExecuteBatchMatchAnalyze

Request Parameters

Response Fields

Usage Example