MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 16 · Environments and promotion

Versioning and rollback

Lesson 159 of 175 · 2 min

Keeping the PREVIOUS version so a bad promotion can be reversed in minutes, and the IN-FLIGHT INSTANCES that complicate it. The rollback plan is decided before the promotion, not during the incident. At 2am with a client on the phone, "how do we put it back" is a question with a five-minute answer or a four-hour one, and which of those it is was determined the previous afternoon. THE MECHANISM IS SIMPLE: KEEP THE PREVIOUS VERSION IN THE TARGET INSTANCE. Do not delete it on promotion. OIC versions integrations, so the old one can sit deactivated beside the new one, and reversing is deactivating the new and reactivating the old — which is minutes. AND THE ROLLBACK IS ONLY MINUTES IF THE OTHER THINGS DID NOT CHANGE, which is the part people miss. If the promotion also edited a lookup, changed a connection, or relied on a new certificate, then…

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.

See the course and enrol9 free lessons

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 16 · Environments and promotion

  1. 1What an environment means here
  2. 2Export and import, mechanically
  3. 3The promotion checklistFree preview
  4. 4Connections do not travel
  5. 5Lookups and environment-specific values
  6. 6Schedules after promotion
  7. 7Versioning and rollback
  8. 8Automating promotion
  9. 9What breaks: four promotion failures
  10. 10Lab briefing · Promote, and prove it is isolated