Oracle Integration Cloud: Building Integrations That Survive Production · Module 16 · Environments and promotion
Automating promotion
Lesson 160 of 175 · 2 min
Scripting export and import for a repeatable release. WORTH IT above roughly a dozen integrations, and PREMATURE below that. OIC exposes an API for export, import, activation and connection management, so the whole promotion can be scripted. The question is not whether it CAN be automated but whether it should be, at this size, on this project. BELOW ROUGHLY A DOZEN INTEGRATIONS, IT IS PREMATURE. The manual promotion takes an afternoon a few times a year. The script takes days to write, needs its own credentials, and becomes a second thing to maintain and to debug — and it is debugged on promotion day, which is the worst day to be debugging anything. The effort is better spent on the checklist being written down and actually followed. ABOVE THAT, THE ARITHMETIC REVERSES AND SO DOES THE RISK PROFILE. Thirty integrations promoted by hand is a full day of repetitive work…
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 16 · Environments and promotion
- 1What an environment means here
- 2Export and import, mechanically
- 3The promotion checklistFree preview
- 4Connections do not travel
- 5Lookups and environment-specific values
- 6Schedules after promotion
- 7Versioning and rollback
- 8Automating promotion
- 9What breaks: four promotion failures
- 10Lab briefing · Promote, and prove it is isolated
