Activate Integrations
On completion of the above configurations, follow the below steps to activate and run the Accelerator.
Note:
The Accelerator Integrations should NOT be executed manually or deactivated during the runtime flow.
Accelerator Integrations
Table 2-9 Integrations
Step | Integration Name | Details |
---|---|---|
1 |
Oracle Hospitality ATP Capture BE |
Main capture business events integration and entry logic. |
2 |
Oracle ATP REST Orchestration |
Orchestration to get the group Id. |
3 |
Oracle REST ATP Producer |
Producer to change status of Business Events to P. |
4 |
Oracle ATP REST Dispatcher |
Gets concatenated payload using group Id and delivers the message to external system. |
Table 2-10 Integrations
Step | Integration Name — Target | Details — Recipe/custom integration that will communicate with the external system |
---|---|---|
5 |
Oracle EXT_SYS ATP Dispatcher Log Status |
Marks group as C (logging if flag is enabled) and exits logic. |
6 |
Oracle EXT_SYS ATP Error Message Handler |
Filters messages from scope/global fault handlers and sends error mail. |
Integration to be Manually Activated only on Error, Post Fix
Table 2-11 Integrations
Integration Name | Details — of integration called manually for error scenarios |
---|---|
Oracle REST REST Error Flag Reset |
Resets the flags in the configuration table and business queue table and calls the Capture Business Events Integration to restart processing of the Accelerator. |
Parent topic: Oracle Integration Cloud (OIC) Artifacts