MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 11 · Lookups, libraries and reuse

JavaScript libraries in OIC

Lesson 112 of 175 · 2 min

When the mapper cannot express something. The narrow set of cases that justify code, and the maintenance it adds. The mapper handles the overwhelming majority of transformation, and Module 5 covered its functions in depth. A JavaScript library is the escape hatch for what it genuinely cannot do. THE HONEST LIST IS SHORT. A non-trivial algorithm — a checksum, a check-digit calculation, a hash. A parse of a string with a structure the mapper's string functions cannot decompose. A date arithmetic the built-ins do not offer. Genuine cases, and rare. WHAT DOES NOT JUSTIFY IT is the case that produces most of the libraries in a real estate: "the mapping was getting complicated so I moved it into code." That is a transformation nobody can read from the mapper — the mapping now shows a function call and nothing about what it does — and it is usually a sign

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.

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 11 · Lookups, libraries and reuse

  1. 1Lookups: the cross-reference table
  2. 2Editing a lookup safely
  3. 3JavaScript libraries in OIC
  4. 4Reusable connections and naming
  5. 5Configuration versus hard-coding
  6. 6What breaks: the lookup nobody owned
  7. 7Lab briefing · Externalise the hard-coded values