Oracle Integration Cloud (OIC) is a cloud-based integration platform offered by Oracle that allows organizations to connect various applications, systems, and services to streamline business processes and data flows. In OIC, “Trigger” and “Invoke” are terms related to integration patterns and actions within the platform.

1. Trigger: A trigger in Oracle Integration Cloud refers to an event or an action that initiates an integration flow. It’s the starting point of an integration process. Triggers can be events from various sources such as applications, databases, files, or REST APIs. When the trigger event occurs, it kicks off the integration flow, allowing you to process data, perform transformations, and route it to the desired endpoints.

Examples of triggers in OIC:

• File-based Trigger: An integration flow can start when a file is uploaded to a specific directory.
• Scheduled Trigger: Integration can be triggered at a specific time or interval.
• REST Trigger: An integration can start when a REST API endpoint receives a request.

2. Invoke: In Oracle Integration Cloud, “Invoke” refers to the action of calling or executing an integration process or a specific integration interface. When you invoke an integration, you are essentially initiating the execution of a predefined integration flow that processes data from the source to the target endpoint based on your defined mappings, transformations, and logic.

There are different ways to invoke integrations in OIC:

• Synchronous Invocation: The caller waits for the integration to complete and receives a response immediately.
• Asynchronous Invocation: The caller initiates the integration but doesn’t wait for its completion. This is useful when the integration takes time to process.

In OIC, you can design integration flows visually using the integration designer, where you define the triggers, mappings, transformations, and endpoints. The platform provides a range of connectors to various applications and systems, making it easier to create integrations without the need for extensive coding.

Here’s a simplified example of how Trigger and Invoke work together in OIC:

1. Trigger Configuration: You set up a trigger that listens for new data in a specific folder.
2. Integration Flow: When the trigger event occurs (a new file is added to the folder), the integration flow is invoked.
3. Data Transformation: The integration flow retrieves the file data, performs necessary transformations, and maps it to a target structure.
4. Invoke Action: The integration flow invokes another service (e.g., REST API, database) to send the transformed data.
5. Completion: Once the data is successfully sent to the target, the integration completes, and you may receive a response or confirmation.