Understand Integration Patterns

You can select from several patterns when creating an integration in the Create integration panel.

What Kind of Integration Should You Design?

When you create an integration, the first decision to make is the integration model to use. The main difference among the models is the way that they start running.

What starts the integration? If it's a business activity or something changing in an application, design an application integration. If it's the clock or a person running the integration on demand, design a schedule integration. If it's another integration publishing a business event, design an event integration

Available Integration Patterns

Pattern	Description
Application	Create an application integration (previously known as app-driven orchestration) that uses an event or a business object to trigger the integration. For example, you create an integration with an Oracle Service Cloud (RightNow) Adapter as a trigger and an Oracle CX Sales and B2B Service Adapter as an invoke. The Oracle Service Cloud (RightNow) Adapter subscribes to an event from the Oracle CX Sales and B2B Service application to trigger the integration. Application integrations include many actions for performing specific tasks, such as the following: Switch actions to create multiple routing expressions. For-each actions for looping over repeating elements. Assign actions for assigning values to scalar variables. Ad-hoc mappings on switch actions branches. Callback actions (to end a process and respond back to the sender) and end actions (to end a process without responding back to the sender) in asynchronous integrations. See About Application Integrations and Create Application Integrations.
Schedule	Create an integration that uses a schedule to trigger the integration instead of an adapter. For example, you add an initial invoke adapter to read a trigger file and a second FTP adapter to download the file for further processing. After designing this integration, you schedule when to run it. See About Schedule Integrations and Create Schedule Integrations.
Event	Create and select events for publishing and subscribing to in integrations. You define the events in JSON-formatted files. Note: If you created integrations using the Publish to OIC and Subscribe to OIC integration patterns (often called pub/sub) in Oracle Integration Generation 2, these capabilities and more are available in Oracle Integration 3. To create an integration that publishes an event, create an application integration. To create an integration that subscribes to published events, create an event integration. See Create Integrations to Publish and Subscribe to Events.

Pattern

Description

Application

Create an application integration (previously known as app-driven orchestration) that uses an event or a business object to trigger the integration. For example, you create an integration with an Oracle Service Cloud (RightNow) Adapter as a trigger and an Oracle CX Sales and B2B Service Adapter as an invoke. The Oracle Service Cloud (RightNow) Adapter subscribes to an event from the Oracle CX Sales and B2B Service application to trigger the integration. Application integrations include many actions for performing specific tasks, such as the following:

Switch actions to create multiple routing expressions.
For-each actions for looping over repeating elements.
Assign actions for assigning values to scalar variables.
Ad-hoc mappings on switch actions branches.
Callback actions (to end a process and respond back to the sender) and end actions (to end a process without responding back to the sender) in asynchronous integrations.

See About Application Integrations and Create Application Integrations.

Schedule

Create an integration that uses a schedule to trigger the integration instead of an adapter. For example, you add an initial invoke adapter to read a trigger file and a second FTP adapter to download the file for further processing. After designing this integration, you schedule when to run it.

See About Schedule Integrations and Create Schedule Integrations.

Event

Create and select events for publishing and subscribing to in integrations. You define the events in JSON-formatted files.

Note: If you created integrations using the Publish to OIC and Subscribe to OIC integration patterns (often called pub/sub) in Oracle Integration Generation 2, these capabilities and more are available in Oracle Integration 3. To create an integration that publishes an event, create an application integration. To create an integration that subscribes to published events, create an event integration. See Create Integrations to Publish and Subscribe to Events.