Oracle Integration Cloud: Building Integrations That Survive Production · Module 11 · Lookups, libraries and reuse
Lab briefing · Externalise the hard-coded values
Lesson 116 of 175 · 2 min
Take an integration with three hard-coded values, move each to the RIGHT place, and justify why that place rather than another. The justification is the exercise. Moving a literal out of a mapping is mechanical; deciding WHERE it goes is the judgement this module exists to teach, and the three values are chosen to have three different answers. AN ENDPOINT URL BELONGS IN THE CONNECTION. Not a lookup — a lookup is a correspondence between codes, and an endpoint is a property of a system. Putting it in a lookup works and puts environment configuration somewhere the promotion process does not look for it. A CODE CORRESPONDENCE BELONGS IN A LOOKUP. Editable by the business, no development change, effective on the next run — Lesson 1 exactly. AND A THRESHOLD IS THE INTERESTING ONE, because it has no obviously right home. A lookup can hold it, and then a business…
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 11 · Lookups, libraries and reuse
- 1Lookups: the cross-reference table
- 2Editing a lookup safely
- 3JavaScript libraries in OIC
- 4Reusable connections and naming
- 5Configuration versus hard-coding
- 6What breaks: the lookup nobody owned
- 7Lab briefing · Externalise the hard-coded values