Oracle Integration Cloud: Building Integrations That Survive Production · Module 1 · What OIC is, and when you need it
The four patterns Fusion already handles
Lesson 6 of 175 · 2 min
Half the requests that arrive at an integration platform are one of four patterns Fusion already handles, and recognising them saves a licence and a project. FILE DROP. Another system leaves a file; Fusion loads it. FBDI and HDL do this natively, with validation, error reporting and a reconciliation path. SCHEDULED EXTRACT. Fusion produces a file on a schedule and delivers it. BI Publisher plus the scheduler does this, including the incremental high-water mark. DIRECT API CALL. One system calls Fusion when something happens. The REST and SOAP services are already there, and a caller that can make an HTTP request does not need a platform in the middle to do it. BUSINESS EVENT. Fusion announces something happened. The event is published whether or not OIC is involved; a receiver that can accept a callback can subscribe directly. SO THE FIRST QUESTION FOR ANY REQUIREMENT IS WHETHER IT IS ONE…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, with a certificate on completion and a fourteen-day refund window.
In this module: Module 1 · What OIC is, and when you need it
- 1What the product actually is
- 2The four patterns Fusion already handles
- 3When you genuinely need OICFree preview
- 4What it costs, and who pays
- 5OIC and the rest of the Oracle estate
- 6Gen 2 versus Gen 3, and why you care
- 7What breaks: the integration that should not exist
- 8Lab briefing · Six requirements, one recommendation each