Integration fundamentals and OCI Application Integration architecture
Domain 1 - Integration fundamentals and OCI Application Integration architecture
This domain tests how Oracle Integration is structured and how a message moves from a trigger to an invoke. Expect questions on design-time versus runtime, connection roles, orchestration styles, and where the connectivity agent fits.
Core rules
- Oracle Integration is a managed service. You design metadata in the Designer (integrations, connections, lookups, packages) and execute instances in the runtime.
- A connection is a reusable endpoint definition; its role is either trigger (starts an instance) or invoke (called by an instance). The same adapter can support different roles.
- Adapters translate between OIC and a protocol or application: REST, SOAP, file/FTP, database, JMS/Kafka, and SaaS adapters such as ERP Cloud.
- App Driven Orchestration is request/event driven and can return a synchronous response. Scheduled Orchestration starts from a schedule and is suited to batch polling. Basic Routing is a lightweight content-based router.
- An on-premises endpoint is reached through a connectivity agent group installed inside the customer network; the agent makes outbound TLS connections to OIC.
Worked example
An ERP Cloud event must create a Salesforce case and return the case ID to the caller. Choose App Driven Orchestration: the ERP Cloud connection is the trigger (not invoke), a Map activity aligns invoice fields to case fields, and a Salesforce invoke returns the ID. The trigger role is essential; an invoke connection cannot start the flow. If the caller needs an immediate answer, keep the response synchronous; if processing is long, return a receipt and use a callback.
Traps
Do not confuse trigger and invoke when creating a connection. Do not use Scheduled Orchestration for an inbound REST request. Do not assume an export carries credentials, and do not expect the agent to require inbound firewall openings.