Table of Contents

Search

  1. Preface
  2. Introduction to Services Integration Framework
  3. Setting Up the SIF SDK
  4. Request and Response Objects
  5. Transactions and Exception Handling
  6. ORS-Specific SIF API
  7. Asynchronous SIF Requests
  8. ORS-Specific JMS Event Messages
  9. Using Security Access Manager
  10. Using Dynamic Data Masking
  11. SIF API Reference
  12. Troubleshooting
  13. Appendix A: Identifiers
  14. Appendix B: Frequently Asked Questions

Services Integration Framework Guide

Services Integration Framework Guide

ExecuteBatchMatch

ExecuteBatchMatch

An ExecuteBatchMatch request calls a match batch job, which runs the match process.

Request Parameters

The ExecuteBatchMatch request contains the following parameters:
TableName
Name of the base object table.
MatchSetName
Optional. Name of the match rule set for the batch job. Default is null.
validateTableName
Optional. Name of the table that contains the row ID values to validate. Default is null.

Response Fields

The ExecuteBatchMatch request returns the following fields:
InteractionId
An identifier for the request.
Message
A brief message about the status of the request.
RetCode
A 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 batch job on a base object table:
SiperianClient sipClient = SiperianClient.newSiperianClient(new File( context.getTestPTTStartDir() + "siperian-client.properties" ) ); ExecuteBatchMatchRequest req = new ExecuteBatchMatchRequest(); req.setTableName(jobContext.getTableName()); req.setMatchSetName(jobContext.getMatchSetName()); while(rc==0) { ExecuteBatchMatchResponse executed = (ExecuteBatchMatchResponse) sipClient.process( req ); errMessage = executed.getMessage(); rc = executed.getRetCode(); completeStep((rc == -21014) ? 0 : rc, errMessage, context, jobContext); } if(rc == -21014) { // SIP-21014: Error registering start of Match failed during post to Cleanse Server: Base Object C_CUSTOMER is empty or no more records to match // Regard it as normal completion so that test could continue the left jobs rc = 0; }

0 COMMENTS

We’d like to hear from you!