MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 17 · Quarterly updates and OIC

Two update calendars, not one

Lesson 163 of 175 · 2 min

OIC and Fusion move on SEPARATE schedules. Which of your artefacts is exposed to which, and why that distinction saves most of the testing. Two platforms, two calendars, and an estate that is exposed to both. Fusion updates on its quarterly cycle; OIC updates on its own. They do not coincide, which is a nuisance and is also the thing that makes this manageable — each update puts a different, smaller part of your estate at risk. A FUSION UPDATE THREATENS WHAT YOU BUILT AGAINST FUSION. Generated structures from the Fusion adapter, business events you subscribe to, BI report definitions, field availability. Module 4's territory, and Module 10's third failure — an event that quietly stops being raised. AN OIC UPDATE THREATENS THE PLATFORM ITSELF. Adapter versions, runtime behaviour, the console, deprecated operations. Your mappings and orchestrations are exposed to this and mostly not to the Fusion calendar. SO THE

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.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 17 · Quarterly updates and OIC

  1. 1Two update calendars, not one
  2. 2Reading an OIC release note for risk
  3. 3Adapter versions and regeneration
  4. 4A regression pack for integrations
  5. 5Testing in the update window
  6. 6What breaks: after the update
  7. 7Lab briefing · Assess a real release note