In April 2026, we saw the release of Oracle Integration 3 26.04 and with it, we yet again see a bunch of new features. In this post I will document some of the key features that you can now take advantage of. Note – for full release information, please visit Oracle documentation here.

As I mentioned in my post: Oracle Integration – Moving to a quarterly release cycle!, Oracle integration has now moved to a quarterly release cycle.

This is Oracle’s 2nd release for the year. To read about the previous OIC release (26.01), see my post here.

---

NEW Common Features

New Common features of Oracle Integration 3 include:

• There are now new service metrics available. They are:

Service Metric	Description
AsyncInboundRequestsDepth	This service metric can be used to show the number of requests that are in the asynchronous queue
FileServerInboundConnections	This service metric can be used to show the number of requested sessions in the file server
SchedulerTriggeredInstancesCount	This service metric can be used to show the number of scheduled integration requests

• Updates have been made to existing service metrics. They are:

Service Metric	Description
NumberOfInboundRequests	This Service metric can be used to show the number of inbound requests. It has been updated with a flowType dimension which can be used to specify the integration flow type as sync or async.
InboundRequestProcessingTime

• New Integration Recipe: Sync new cases from Microsoft Dynamics 365 to ServiceNow

• New Integration Recipe: Extract approved expense reports from SAP Concur and write to an FTP server

• New Integration Recipe: Create AI Assisted clinical care plans

• New Integration Recipe: Leverage RPA to automate group creation and assign users in Oracle ERP – RFRPA

NEW Agentic AI Features

• Agentic AI pattern versioning – you can now version agentic AI patterns with a minor or major version. See my post OCI Integration Fundamentals: Versioning to learn more about how semantic versioning in Oracle Integration works.
• Agentic AI pattern cloning – You can now clone an existing agentic AI pattern.
• Agentic AI pattern activation – You can now natively activate all integrations used by an agentic AI pattern at the same time that the pattern is activated.
• Agentic AI Pattern usage – You can now natively see which patterns are using which integrations
• New out of the box agentic AI patterns:
  • ReAct for Oracle Cloud Infrastructure Generative AI: This can be used to connect to the OCI Generative AI LLMs. It supports xAI and OpenAI models.
  • Plan: This can be used to implement plan and execute within your integrations and use multiple LLMs.
• Errors that arise in the MCP server have been standardised according to the defined MCP specification and therefore improved ease and simplicity of error handling
• It is now possible to version and close AI agents
• It is now possible to change the agentic AI pattern that is associated with a given AI agent
• Project exports now also include the export of AI agents, agentic AI tools, agentic AI patterns, prompt templates, and all of the related integrations and connections necessary within the project.
• Ability to build a knowledge base of documents which can be searched from within an integration. The knowledge base can also be published as a tool to be used.

NEW Integration Features

New integration features of Oracle Integration 3 include:

• Integrations (Standalone or multiple) that are not used by a project can now be copied into a new or existing project
• Enhancements have been made to integration updates so that now when you edit an integration using AI, there is not a need to save the integration each time an AI-generated update has been made.
• OCI Vision native action now allows the use of custom models for image classifications – More coming soon on OCI AI Services x Oracle Integration native actions.. stay tuned.
• OCI Generative AI native action now supports the use of OpenAI and xAI models for chat based functions.- More coming soon on OCI AI Services x Oracle Integration native actions.. stay tuned.
• OCI Document Understanding native action has been enhanced to include a document classification action when using custom models. It means that a customer-trained model can be used specific to documents and business domains of that customer – For more information on OCI Document Understanding native action, see my post: Oracle Integration Cloud: Using the AI Document Understanding Action. More coming soon on OCI AI Services x Oracle Integration native actions.. stay tuned.

NEW/UPDATED Adapters & Connectivity

With this release we see the following new adapters available out-of-the-box:

Adapter	Comment
BigQuer	This new adapter allows seamless integration to Google BigQuery
DataBricks	This new adapter allows seamless integration with the Databricks database residing behind the firewall of your on-premises environment through use of the on-premises connectivity agent.
ActiveMQ	This new adapter allows seamless integration to connect to the ActiveMQ Artemis messaging system

In addition, the following adapters available out-of-the-box have been updated:

Adapter	Update
REST	Now provides support for the Multi-Key authentication security policy Now provides the ability to dynamically update the invoke connection at runtime
Apache Kafka	Now provides support for the SASL/SCRAM security policy
Azure EventGrid	Now provides support for working with both public and private namespaces.
NetSuite REST	Now provides support for JWT Client Credentials assertion
Shopify 2.0	Now provides support for the client credentials security policy
Shopify GraphQL	Now provides support for OAuth 2.0 client credentials security policy. Now provides support for Bulk Module events. Now provides support for Bulk Operations events. Now provides support in the customer module for the following events: Customer purchasing summary, Customer email marketing consent update, Customer SMS marketing consent update, Customer tags added, customer tags removed
GCP Pub Sub	Now provides support to change the topic or subscription in the mapper if a topic or subscription already exists for publishing, pulling or acknowledgement of messages
Salesforce	Salesforce will retired the use of the username password security policy in summer 2027