Automating End to End Bulk Export from Oracle ERP Cloud using Oracle Integration (Part 2- ERP Cloud Event based Callback)

Background

In Part 1 of the blog series we have seen how to Initiate Oracle ERP Cloud Data Extract process from OIC. We have also seen how a callback url can be used to trigger the Callback Integration Flow after the BIP extract job is complete. In this blog we will witness the out of box event based mechanism to trigger the Callback Integration flow instead of a concrete callback endpoint. The best practice is to leverage event based mechanism as there is built in retry mechanism in ERP Cloud if the event is not delivered to OIC.

Designing the Integration Flow

Prerequisite Configuration

Refer: Configure Section of ERP Cloud

Modify the ERP Bulk Extract Integration flow (Flow 1- Refer Part1)

Update the Map fields for erpBulkExport Operation to the following literal values

• jobOptions: "EnableEvent=Y"
• callbackURL: Do not provide anything. Delete the mapping if it exists

Activate the Integration Flow

Creating Event based Integration Flow (Flow 2)

1. Create an App Driven Integration flow

2. Drop ERP Adapter Connection and configure "ERP Integration Outbound Event". This event is triggered after exportBulkData is completed via ERPIntegrationService

3. Use SOAP Adapter Connection configure ERPIntegrationService->getDocumentForDocumentId which fetches the data extract attachment from UCM

Accept Attachments in response allows to process files as big as 1 GB

4. unzipExtract - Stage file activity uses unzip operation to unpackage the report files into OIC virtual file system

5. listFiles - Stage file activity uses listFiles operation which lists all the files unzipped for a given directory in OIC virtual file system

6. writeFile - Uses FTP connection to write the report xml file to configured directory in ftp server

Testing the End to End Integration Flow

1. Run the ERP Bulk Extract Integration. Make a note of Request Id

2. In the ERP Cloud Scheduled Processes. Verify the job corresponding to Request Id

3. Observe the trigger payload in the event based integration

Here is few advantages of leveraging Event based callback flows as compared to URL based callback flows

• Need not create an explicit Interface WSDL to implement onJobCompletion operation
• Event is natively supported by Oracle ERP Cloud Adapter which protects from any changes in ERP Cloud interface changes just in case. 
• Needless to mention we can avoid all the additional steps to capture JSON and parse the same. Event payload is parsed and readily available in the trigger message to fetch the report from UCM
• When an Event based integration is activated OIC creates a subscription entry in Oracle ERP Cloud. For some reason if the Event based Integration Flow is not reacheable ERP Cloud will re-try the events multiple times with exponential time gap. In the URL based callback re-try cannot happen as it is a fire and forget from ERP Cloud