Introducing Oracle Integration MCP Gateway: Governed Access for Enterprise AI Agents by Kishore Katta
AI agents are becoming more useful when they can do more than answer questions. They can retrieve enterprise information, trigger workflows, coordinate actions across systems, and help employees complete work faster.
But as agents gain access to enterprise tools, organizations need to maintain control over who can access what, which tools are available, how credentials are handled, and how activity is monitored.
That is where Oracle Integration MCP Gateway comes in.
Oracle Integration MCP Gateway is part of Oracle Integration (OIC). Oracle Integration MCP Gateway features will be available in the Oracle Integration 26.10 release, providing a governed path for MCP clients to access OIC and approved third-party MCP servers with centralized identity, policy, credential, enforcement, and observability controls.
A governed foundation for enterprise AI
Oracle Integration helps organizations connect applications, data, processes, and people. It provides capabilities for:
• Connecting to applications, APIs, services, and data.
• Building integrations and automations across systems.
• Applying business decisions and rules.
• Orchestrating multi-step agent interactions.
• Including people in approvals, reviews, and exception handling.
Oracle Integration MCP Gateway extends this foundation to Model Context Protocol (MCP) interactions.
The future of OIC Process Automation by Stan Tanev
For twenty years we automated processes by drawing every possible path in advance. Agents now let us describe the work instead, and put determinism only where it earns its place. This paper lays out the patterns in use today, the architecture we believe all of it converges on, and how Oracle Integration gets you there by reusing what you already run.
The arrival of agents
Business process management gave us a shared language. BPMN turned a whiteboard sketch into an executable model: a lane for every owner, a diamond for every decision, and a task for every step. CMMN followed for work that refused to be sequenced: a case worker chose the order, but the tasks were still modeled ahead of time. Both standards therefore rest on the same premise: someone has to anticipate the possibilities in advance, and update the model when the business changes.
Until recently, the limits of software left no other way to model processes, so automation took the well-travelled path, and the judgement calls, the incomplete inputs, the customer whose case fit no template stayed manual. When the business changed, updating the process definition often required IT involvement and funding for a new project.
From Global Integrations to Projects: A Safer Path to Innovation by Prakash Masand and Pradyumna Kodgi
Oracle Integration is moving toward a more Project-centric operating model. Projects provide a better way to organize, secure, deploy, and operate integrations as complete business solutions rather than managing each integration as a standalone asset.
Many customers already have production integrations running in the global integration model. These integrations may be consumed by downstream applications and tied to existing runtime URLs, so moving them into projects must be handled as a controlled transition. With the 26.10 release, two major blockers are addressed: preserving existing runtime URLs and moving integrations at scale.
Why Move to Projects?
Customers should move existing integrations into Oracle Integration Projects to adopt the newer operating model for building, securing, deploying, observing, and exposing integrations for intelligent automation.
1. Adopt new AI and agentic capabilities
New AI-assisted and agentic capabilities are increasingly project-focused. Moving to projects prepares customers for intelligent integrations, AI-assisted development, agentic patterns, and smarter operations.
2. Enable MCP and agent-ready integrations
Projects provide a natural way to expose selected integrations as governed capabilities for AI agents through MCP. This helps customers make existing integrations agent-ready while keeping ownership, access, and lifecycle management aligned to the project model.
Modernizing Oracle SOA B2B with a Hybrid Transition Approach by Pradyumna Kodgi & Ravi Pinto
Oracle SOA Suite customers using B2B are approaching an important modernization decision.
Oracle Fusion Middleware 12c Premier Support ends in 2026, followed by Extended Support in 2027. In addition, Oracle SOA Suite 14c does not support B2B document protocols, including EDI, EDIFACT, HL7, and PFF.
For additional details on the applicable support timelines and guidance, refer to the relevant Oracle Support note: Oracle Support Note: 11757334.
Once B2B workloads have been transitioned from SOA B2B to Oracle Integration B2B, customers can proceed with upgrading their remaining SOA workloads to SOA Suite 14c.
For customers using these capabilities, Oracle Integration B2B provides a practical path forward.
There are two broad modernization approaches:
• Hybrid Transition — move the B2B edge to Oracle Integration while continuing to use existing SOA integrations.
• Re-platform to Oracle Integration — progressively move SOA integrations to Oracle Integration as part of broader platform modernization.
In this blog, we focus on the Hybrid Transition approach. We will cover re-platforming in more detail in a subsequent blog later point in time.
Long-Term Audit and Operational Insight for Human in the Loop by Stan Tanev
Approvals are where automation meets accountability. When a purchase order is held for sign-off, an expense is rejected, or an AI agent pauses to ask a person before it acts, somebody will eventually ask: who approved this, when, and why? Sometimes that question comes a week later. Sometimes it comes from an auditor eighteen months later.
With 26.10, Human in the Loop (HITL) in Oracle Integration can now publish its activity stream to OCI Log Analytics. Every workflow and task state change becomes a structured log record that you can retain for as long as your compliance policy requires, query with the full Log Analytics query language, and monitor through a pre-built Oracle Integration: HITL dashboard.
This post is a deep dive into that feature: why it matters, how to set it up, how to search the logs, and what the dashboards give you out of the box. If you want the full picture of everything in 26.10, start with Niall’s What’s New in Oracle Integration 26.10.
Why you should care
1. Durable retention for audit and compliance
HITL runtime data lives inside Oracle Integration and follows the instance’s data retention setting. By default that is 32 days for Standard and Enterprise edition instances (184 days for Healthcare edition), and only Enterprise edition can raise it — to a maximum of six months. The clock starts when a workflow reaches a terminal state: active workflows are never purged, but once an instance is Completed, Faulted, Expired or Terminated, it and all of its task history are deleted after the retention period elapses.
For day-to-day operations that is plenty. For audit trails it usually is not. Financial approvals, HR decisions, and regulated processes routinely need to be reconstructible years after the fact, long after the workflow itself has been purged.
Log Analytics closes that gap. Once publishing is enabled, each HITL event is pushed to a log group that you own, in your tenancy, with the retention period you configure. The data outlives the workflow instance, and it lives alongside the rest of your OCI observability data rather than in a silo.
New Adapters and Connectivity Enhancements in Oracle Integration 26.10 by Madhav Poosarla
Oracle Integration 26.10 continues to expand enterprise connectivity and intelligent automation, delivering new adapters and enhancements across agent-driven workflows, AI native actions, event processing, security, data integration, and cloud connectivity.
This release enables customers to invoke Fusion agents from integration flows, work with MongoDB document data, use OCI Generative AI native actions across supported regions and environments, and connect to a wider range of OpenAI-compatible providers. It also adds enhanced authentication options for SAP SuccessFactors and other enterprise applications, expands public gateway, private endpoint, and Connectivity Agent access where supported, and provides new configuration options for database and messaging integrations.
The following highlights provide an at-a-glance summary of the new adapters, AI native action and data enhancements, adapter updates, security and connectivity enhancements, and other updates in this release.
Connect Claude to your Oracle Integration tools by Stan Tanev
Oracle Integration lets you expose a project as a Model Context Protocol (MCP) server. MCP is the open standard AI clients use to discover and call tools, so once a project is MCP-enabled, any MCP-capable client can discover the integrations you have registered as tools and call them under the identity of the person using that client. Claude is one of the most widely used of those clients, and many of you have asked how to connect it with Oracle Integration. This post is that guide: defining three pieces to configure (OCI IAM, Oracle Integration, and Claude), explaining how the OAuth authorization code flow ties them together, and which of Claude’s authentication options to pick and why.
To keep the walkthrough concrete, the example throughout is a small GetWeather integration that looks up a forecast for a city. It stands in for the integrations you already run and would like your people to reach from a chat window. The setup is identical for all of them, and the only thing that changes is the description you give the tool. By the end, a user in your organization can open Claude, ask a question in plain language, and have Claude call the integration you exposed and answer from the result.
Oracle Integration Cookbook for Oracle ERP Cloud by Juan Jesús Montero Rodríguez & Sadia Tahseen
A Hands-On Guide to Build Enterprise Integrations
The book begins by establishing a strong foundation, introducing OIC concepts, integration types, adapters, connections, fault handling, notifications, mappings, JavaScript, XSLT, projects, and monitoring capabilities. It then dives deep into the heart of Oracle ERP Cloud integrations, covering REST, SOAP, FTP, ATP databases, Object Storage, Visual Builder, BI Publisher, UCM Web Center, and ERP Business Events. Readers are guided through detailed, step-by-step demos including FBDI-based integrations, callback patterns, event-driven architectures, advanced REST and SOAP use cases, file-based processing, parallel and data-stitch activities, massive data loads, and delta-based processing between runs.
The final chapters and appendices provide advanced demos, troubleshooting techniques, Postman and SoapUI usage, reusable samples, and best practices, making the book an invaluable reference for both day-to-day delivery work and long-term architecture design. By the end of this book, readers will not only understand how Oracle ERP Cloud integrations work, but will also have the confidence and practical knowledge to design, build, monitor, and optimize robust, scalable, and production-ready integration solutions using Oracle Integration Cloud.
You Will:
• Design, build, and monitor end-to-end integrations between Oracle ERP Cloud and external systems using Oracle Integration Cloud (OIC)
• Implement and troubleshoot real-world integration scenarios using REST, SOAP, FTP, FBDI, ERP Business Events, ATP databases, Object Storage, and Visual Builder
• Apply advanced integration patterns including callbacks, event-driven flows, parallel processing, massive data loads, delta processing, fault handling, and production best practices
This book is for : Oracle Integration Cloud (OIC) developers, Oracle ERP Cloud consultants and integration architects
|
