Oracle ATP REST Orchestration

The Oracle ATP REST Orchestration integration is the heart of the solution and it is where the re-sequencing occurs. This integration will be triggered corresponding to each external system from the previous integration. It calls a stored procedure that returns the Group ID assigned to all the business events that are currently picked and then sent to the Producer integration to be processed.

Integration Flow

Figure 2-11 ATP REST Orchestration

Integration Description

Receive External System ID

Get the External System ID to be processed from the previous integration.

Retrieve Group ID

Integration that invokes the stored procedure OHIP_OIC_GET_GROUP_ID_SP to get a new Group ID for the Business Events.

The stored procedure uses a View to sort the business events based on the following: business event timestamp, batch timestamp, events sequence, business event id, and in this specific order. This procedure groups the business events together and assigns a group id based on the following criteria:

• Payload size up to Max 5 MB

• Maximum number of business events defined in the configuration table

• Among the above to values (whichever one it meets first)

• Business events for which Parking time (defined in the configuration table) has elapsed

The Group ID is used for processing the business events together. 

When the business events have not been in the Q table for the parking time amount, then no Group ID is returned. In this case, send status = 'RP' (Reprocess) to the dispatcher log integration after waiting for the remainder of parking time (calculated in the database and returned by the procedure).

Invoke Producer Integration

Send Group ID assigned from above to the Producer Integration.