Oracle Integration Cloud (OIC) is Oracle’s cloud-based platform for connecting applications, automating business processes, and building web or mobile interfaces, all from a single service. It provides prebuilt connectors to over 130 applications and technologies, letting organizations move data between cloud apps, on-premises systems, and third-party services without writing integration code from scratch. The current version is Oracle Integration 3.
Core Capabilities
OIC bundles several tools under one roof. The central piece is its integration engine, which lets you design data flows between applications using a visual, drag-and-drop interface rather than hand-coded scripts. You map fields from one system to another, set conditions for when data should move, and schedule or trigger those flows based on events.
Beyond basic integration, the platform includes:
- Process Automation: A visual designer for modeling and running business workflows like approval chains, onboarding sequences, or procurement requests. You can add human approval steps (“human in the loop”) so certain records require a person to sign off before the process continues.
- Visual Builder: A low-code tool for creating web and mobile applications that connect directly to the data flowing through your integrations.
- File Server: A managed file-transfer service for exchanging files with trading partners or internal systems using standard protocols like SFTP.
- B2B: Support for business-to-business document exchange using EDI standards, useful for supply chain and logistics communications.
- Decisions: A rules engine where you model business logic (pricing rules, eligibility checks, approval thresholds) visually, then call that logic from your integrations or processes.
- Robotic Process Automation (RPA): Bots that can interact with application user interfaces to automate tasks in systems that lack APIs.
Not every capability is available in every edition. Process Automation, B2B, Decisions, RPA, and the AI assistant are exclusive to the Enterprise edition. The Standard edition covers integrations, standard adapters, Visual Builder, File Server, and prebuilt recipes.
Adapters and Connectivity
The adapter library is the practical backbone of OIC. Oracle maintains 133 prebuilt adapters covering SaaS platforms, messaging systems, databases, cloud infrastructure, and enterprise applications. These include connectors for Salesforce, SAP, ServiceNow, Workday, Microsoft products, Amazon S3, Apache Kafka, Azure Service Bus, Snowflake, HubSpot, PayPal, QuickBooks, and many others.
Each adapter handles the authentication, API calls, and data formatting for its target system, so you configure connections through a wizard rather than writing raw HTTP requests. Some adapters can both trigger an integration (respond to an event in the external system) and invoke actions in it, while others only support one direction.
Oracle distinguishes between standard adapters, which cover most SaaS and technology connections, and enterprise adapters. Enterprise adapters connect to older on-premises Oracle systems like E-Business Suite, JD Edwards EnterpriseOne, and Siebel, plus SAP’s on-premises products. These enterprise adapters require the Enterprise edition.
For on-premises systems that sit behind a firewall, OIC uses a connectivity agent you install in your local network. The agent creates an outbound connection to OIC so data can flow without opening inbound firewall ports. In Oracle Integration 3, the agent requires JDK 17.
Prebuilt Recipes and Accelerators
Rather than building every integration from zero, OIC offers prebuilt recipes: templated integration flows for common scenarios. These cover connections between popular platforms like syncing contacts between Salesforce and Oracle CX, pushing invoices from Oracle ERP to a financial reporting tool, or routing files from Amazon S3 into a database. Oracle also provides prebuilt “accelerators” for end-to-end business processes such as request-to-receipt, recruit-to-pay, and lead-to-invoice. You import a recipe, customize the field mappings and business rules to fit your environment, and activate it.
Standard vs. Enterprise Edition
OIC comes in two editions, and the gap between them is significant.
The Standard edition gives you the integration engine, standard adapters (covering most SaaS and technology connectors), Visual Builder, File Server, and access to prebuilt recipes. It also includes LLM adapters and OCI AI services for working with large language models. Data retention is 32 days.
The Enterprise edition adds everything in Standard plus Process Automation, B2B document exchange, the Decisions rules engine, enterprise adapters (E-Business Suite, JD Edwards, Siebel, SAP), robotic process automation, an AI assistant, an MCP server, a knowledge base, agentic AI capabilities, human-in-the-loop workflow steps, and disaster recovery (at extra cost). Data retention is also 32 days by default, with the option to extend it for an additional fee.
If your primary need is connecting cloud applications and moving data between them, Standard may be sufficient. If you need to orchestrate multi-step business processes, connect to legacy Oracle or SAP on-premises systems, or use RPA bots, you need Enterprise.
What Changed in Oracle Integration 3
Oracle Integration 3 (sometimes called “Gen 3”) is the current generation and brought several architectural changes from the previous Generation 2.
On the administration side, billing and message analytics moved into the Oracle Cloud Console, and database storage management is now handled entirely by Oracle. Notifications were simplified to hourly and daily reports, dropping the separate critical health alert and integration error notifications that existed before. Custom endpoints now route runtime traffic directly without redirection.
For developers, the biggest changes are practical. REST API calls now encode the integration identifier with a pipe symbol instead of the previous %7C encoding. Instance IDs switched from numeric to alphanumeric values. The REST Adapter consolidated its metadata options into a single field for OpenAPI specifications, replacing the old separate Swagger URL option. Basic authentication for Oracle-provided REST APIs was removed in favor of OAuth.
A few features were dropped entirely. The basic routing and file transfer integration styles no longer exist. If you’re upgrading from Gen 2, you need to migrate basic routing integrations to application integrations first. Several adapters were also removed, including connectors for Automation Anywhere, Evernote, and UiPath RPA (Oracle’s own RPA capability replaces the third-party RPA connectors). The Insight monitoring capability was replaced by Oracle Log Analytics and Process Automation Analytics.
Typical Business Scenarios
OIC is designed for organizations that run multiple cloud and on-premises applications and need data to flow between them without manual rekeying. Common scenarios include syncing employee records between an HR system and payroll, pushing sales orders from a CRM into an ERP, automating invoice processing by extracting data from PDF documents using OIC’s document understanding actions, managing files in Oracle Cloud Infrastructure storage buckets, and processing large data files with built-in operations for row counting and column aggregation.
Healthcare organizations get a specialized FHIR adapter (Fast Healthcare Interoperability Resources), which supports the standard data format used for exchanging patient records between clinical systems. This includes resource mapping, customization, and service interaction capabilities built directly into the adapter.
For organizations already running Oracle Cloud ERP, HCM, or CX applications, OIC has a distinct advantage: its adapters for those products are built in collaboration with Oracle’s own application development teams, providing native access to events and business objects that third-party integration tools would need to approximate through generic API calls.