MSAMM
Back to course

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

Adapter versions and regeneration

Lesson 165 of 175 · 2 min

When a generated structure goes stale, what regenerating changes, and THE MAPPING THAT QUIETLY LOSES A FIELD WHEN YOU DO. Module 4 established that the adapter GENERATES a structure at design time and that the generated copy is a snapshot. The source can change underneath it — a Fusion update adds fields, renames one, changes a type — and your integration goes on using the old shape until something breaks. REGENERATING REFRESHES THAT SNAPSHOT, AND THAT IS THE MOMENT OF RISK RATHER THAN THE FIX. The new structure replaces the old one, and the mapper reconciles what it can. Fields that still match keep their mappings. Fields that were renamed do not match anything, so THEIR MAPPINGS ARE DROPPED — silently, because from the mapper's point of view the target field simply no longer exists. SO THE FAILURE IS A FIELD THAT USED TO BE POPULATED AND NOW IS NOT,

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