Oracle Integration Cloud: Building Integrations That Survive Production · Module 11 · Lookups, libraries and reuse
Reusable connections and naming
Lesson 113 of 175 · 2 min
Conventions that make an estate legible to somebody who arrives after you, decided ONCE rather than per integration. Twenty integrations named by twenty people is not an estate, it is a pile. The cost lands on the person who joins in year two, opens the console, and cannot tell from the list which flows touch payables, which are scheduled, which are the retry companions of others. A NAME SHOULD ANSWER THREE QUESTIONS FROM THE LIST ALONE: what system, what object, what direction. ERP_Supplier_Outbound answers all three; SupplierSync2 answers none and raises a fourth. Pick a shape and apply it to everything, including the flows you think are temporary — the temporary ones are the ones still running in year three. CONNECTIONS ARE REUSED, WHICH MAKES THEIR NAMES MATTER MORE THAN INTEGRATIONS'. One connection serves many integrations, so its name is read far more often than it is written, and a…
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.