When we create an OIC Integration using an EVENT or Business Object as Trigger for an Integration.

Example :

Use Case 1 – Exposing an Integration as an REST API or SOAP API via OIC.

Use Case 2 – Orchestration polling a FTP server, gets a trigger on receiving a file. Example data in csv format etc.

Scheduled Orchestrations are designed for the use case, when we have a requirement for triggering Orchestration flow at specific datetime or day or interval.

Example :

• Use Case 1 – We need to run an interface everyday 9:00 am EST, to pick a file from FTP location, read the data from the file and enrich the data to load that data to Oracle Database. May be another application needs to access this data from Oracle DB but that sync of data is required before 10:00 am EST for Business.

• Use Case 2 – Schedule an Integration to run everyday to get the Currency Exchange Rates from xe.com or oanda.com at fixed interval of time of the day and load that data to Oracle ERP Fusion Cloud.

To understand more, you should refer to Oracle : OIC Scheduler- Decoupled Scheduler and Business Logic Pattern

File Transfer Design Pattern is used for scenarios where we have to manage files from one system to another. The Integrations with strong requirements for MFT, should be design and built using OIC “File Transfer”.

Example :

Use Case 1 – One file needs to be transferred from one FTP location to Multiple FTP servers.

Use Case 2 –

Basic Routing Integration is created initially with empty Trigger and Invoke connections. This design is adopted with the use case, when we have an requirement of integrating business entity of one system to another, with their mapping data structure for request and Response.

We can create only SINGLE routing expression in Basic Routing integration. In case we have an requirement for creating multiple routing expressions, we should use Orchestration Design pattern.

Example:

Use Case 1 –  System A is an ERP Cloud application, any update on an item in your PRODUCT data hub needs to sync to System B. In this case System A is capable of generating an EVENT and updated item change can be TRIGGERED by EVENT and OIC (Using Connection for SystemA ) is listening to that event and map the data the structure required by System B.

In this use case only single routing expression is there and enrichment of data as per mapping requirements for request / response will be designed and built.

This design pattern is used for Building EDN based design, publishing messages to internal Oracle Integration Messaging.

This design pattern is used for Building EDN based design, subscribing messages from internal Oracle Integration Messaging.