Oracle Integration Cloud: Building Integrations That Survive Production · Module 11 · Lookups, libraries and reuse
Configuration versus hard-coding
Lesson 114 of 175 · 2 min
Endpoints, thresholds and codes that differ per environment. What MUST be configurable for promotion to work at all — which Module 16 depends on. This is the lesson Module 16 assumes you have already applied, and an integration that ignores it cannot be promoted: it must be edited on arrival in each environment, which means the thing running in production is not the thing that was tested. THE VALUES THAT DIFFER ARE PREDICTABLE, so identify them before you write a single mapping. Every endpoint URL. Every credential. Every file path and directory. Every notification address — the alert that goes to the team in test must not go to the client in production. Every identifier that names an environment-specific record: a business unit, a ledger, a code that exists in one instance and not the other. AND THE ONES PEOPLE MISS ARE THE SMALL ONES. A threshold above which something…
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.