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

ExecuteBatchLoad

ExecuteBatchLoad

ExecuteBatchLoad calls the Load batch job.

Request Parameters

The ExecuteBatchLoad request contains the following parameters:
TableName
Specifies the staging table name. Required.
ForceUpdateInd
If the value is 0,
MDM Hub
only loads data that has a more recent late updated date than the data in the hub.
If the value is 1,
MDM Hub
loads the data regardless of the last updated date.
Default is 0. Optional.

Response Fields

The ExecuteBatchLoad API returns the following fields:
InteractionId
Contains the interaction ID.
Message
Contains a message regarding the status of the request.
RetCode
Contains the return code.

Usage Example

The following example runs the Load batch job on a staging table:
SiperianClient sipClient = SiperianClient.newSiperianClient(new File( context.getTestPTTStartDir() + "siperian-client.properties" ) ); ExecuteBatchLoadRequest req = new ExecuteBatchLoadRequest(); req.setTableName(jobContext.getTableName()); // STG table name ExecuteBatchLoadResponse executed = (ExecuteBatchLoadResponse) sipClient.process( req ); String errMessage = executed.getMessage(); int rc = executed.getRetCode();

0 COMMENTS

We’d like to hear from you!