MSAMM
Back to course

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

Lookups and environment-specific values

Lesson 157 of 175 · 2 min

The values that legitimately differ per environment, and why Module 11 insisted they be configurable rather than mapped inline. This is where Module 11 Lesson 5 gets paid back, and where an integration that ignored it becomes unpromotable. THE VALUES THAT DIFFER ARE PREDICTABLE: business unit and ledger identifiers, batch sizes, thresholds, notification addresses, file directories, and every code that exists in one instance and not another. Each is legitimately different — nobody is doing anything wrong — and each must be reachable without editing the integration. IF IT IS IN A LOOKUP OR A CONNECTION, PROMOTION IS THE CHECKLIST FROM LESSON 3. Import, correct the value in the target, activate. The integration itself is untouched and therefore still identical to the one that was tested. IF IT IS HARD-CODED IN A MAPPING, THE INTEGRATION MUST BE EDITED AFTER ARRIVAL — AND THAT BREAKS THE INVARIANT FROM LESSON 1. 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.

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