Oracle Integration Cloud: Building Integrations That Survive Production · Module 2 · The console and your first integration
Versions and cloning
Lesson 19 of 175 · 2 min
Editing a live integration versus cloning to a new version, and the consequence of getting it backwards on a production flow. EDITING changes the thing callers are using. Deactivate, change, reactivate — and during that window the endpoint is unavailable, and afterwards every caller gets the new behaviour whether they were ready or not. There is no boundary: the change simply is the integration now. CLONING TO A NEW VERSION creates a separate artefact, which can be built, activated and tested while the current one keeps running. Callers move when they are ready, and the old version is retired once nothing is using it. WHICH ONE YOUR CHANGE NEEDS. Editing is fine for a flow nothing external calls yet, in a non-production environment, or for a fix so small and urgent that a brief outage is the lesser cost. Cloning is correct for anything with live callers, anything changing 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.
In this module: Module 2 · The console and your first integration
- 1The console, and the four places you will live
- 2Projects, and whether to use them
- 3Your first integration, start to finish
- 4Activation, and what it actually does
- 5Running it, and finding the instance
- 6Naming, and why it matters more than it should
- 7Versions and cloning
- 8What breaks: the first-week mistakes
- 9Lab briefing · Build, activate, run, find