OIC Integration : Supplier : Supplier Interface from Cloud to EBS : PLSQL Concurrent Program

 Int : Supplier : Supplier Interface from Cloud to EBS : PLSQL : Concurrent Program 

Difference between synchronous and asynchronous in oic

 Difference between synchronous and asynchronous in oic

In Oracle Integration Cloud (OIC), the terms synchronous and asynchronous refer to the communication pattern between systems or within integrations — specifically, how the sender and receiver interact in terms of waiting for a response.

🧠 Quick Mnemonic:

• Synchronous = "Stop and wait"   5 min (300 sec)

• Asynchronous = "Send and go" 6 hrs async with schedule 

🔄 Synchronous Integration

📌 Definition:

A synchronous integration waits for a response after sending a request. The client (caller) is blocked until the OIC integration finishes processing and returns a result.

✅ Key Characteristics:

• Real-time interaction

• Immediate response required

• Integration returns data or a status to the requester

• Timeouts are important to manage

• Often used in API-like interactions (e.g., REST/SOAP)

📦 Example:

An external system calls a REST-triggered integration in OIC to validate a customer. The integration calls Oracle ERP, gets the validation result, and returns it immediately to the caller.

---

🔁 Asynchronous Integration

📌 Definition:

An asynchronous integration does not wait for a response. The caller sends a request and continues without waiting for the process to complete.

✅ Key Characteristics:

• Fire-and-forget behavior

• No immediate response; may use callbacks, queues, or notifications if needed

• Suitable for long-running or batch processes

• Common in event-driven or scheduled flows

📦 Example:

An ERP system sends a file to OIC. OIC picks up the file (via File/FTP trigger), processes the data, and stores it in a database — no response is sent back to ERP.

---

🔁 Comparison Table

Feature	Synchronous	Asynchronous
Communication style	Request-Response	Fire-and-Forget
Caller waits for reply	Yes	No
Response	Required (status or data)	Optional (via callback or notification)
Best for	Real-time APIs, UI-driven requests	Background jobs, long processes
Complexity	Simple	Can involve callback or correlation
Error handling	Handled inline in response	Often handled via logging or alerting

---

🔧 Real-world Example in OIC:

Scenario	Type
REST API call that returns order status	Synchronous
Scheduled job that loads 10,000 records to ERP	Asynchronous

Connection Types Invoke and Trigger

Connection Types Invoke and Trigger

In Oracle Integration Cloud (OIC), the terms "trigger" and "invoke" refer to how integrations are initiated and how they interact with external systems. Here’s a clear comparison of the two:

Mnemonic means a special word used to help a person remember something

• Trigger = “How it starts”

• Invoke = “Who it talks to”

🔹 Trigger in OIC Definition:

A trigger is the entry point of an integration. It defines how an integration is started—usually by an event or incoming request from an external system or application.

Common Trigger Types:

• HTTP Trigger / REST Adapter – An HTTP request initiates the integration.

• SOAP Adapter – A SOAP request triggers the integration.

• Scheduled Trigger – Integration is triggered based on a time schedule (e.g., every hour).

• Event-based Triggers – For example, receiving a file, or a message on a queue.

Example Use Case:

A REST API call from an external system (like Salesforce) triggers an integration in OIC to process data and store it in Oracle ERP.

🔹 Invoke in OIC Definition:

An invoke is used to call an external system or service from within an integration flow. It's an outbound call to perform some action or retrieve data.

Common Invoke Examples:

• Calling a REST API of another system.

• Sending data to a database.

• Invoking a SOAP web service.

• Pushing data to Oracle SaaS or on-premise systems.

Example Use Case:

An integration fetches employee data from Oracle HCM using an HCM adapter invoke after being triggered by a scheduled job.

Feature	Trigger	Invoke
Purpose	Starts an integration	Calls an external system or service
Direction	Inbound (into OIC)	Outbound (from OIC to another system)
Adapter Type	Trigger-type Adapters	Invoke-type Adapters
Examples	REST trigger, File trigger, Schedule	REST invoke, SOAP invoke, DB invoke
When Used	At the start of an integration	Within an integration (after trigger)