Oracle Integration Cloud: Building Integrations That Survive Production · Module 6 · Orchestration patterns
Lab briefing · Build a four-step flow
Lesson 69 of 175 · 2 min
Read a file, look up each record, branch on a condition, and write results — then MAKE RECORD SEVEN FAIL and see what the run does. Build it in that order and name every step for what it does, per Lesson 2. Four steps is small enough to hold in your head, which is what makes the failure behaviour visible. Give the switch a DEFAULT branch that does something — Lesson 3 — and put a record in your file that matches nothing, so the default is exercised rather than assumed. THEN MAKE RECORD SEVEN FAIL, and that is the exercise. A lookup that finds nothing, a value the target rejects — something realistic. Run it and answer three questions from monitoring alone. ONE: did records eight to twenty process? That is sequential-versus-parallel and continue-on-error, and the answer is a property of how you built it rather than of the…
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 6 · Orchestration patterns
- 1App-driven versus scheduled
- 2Invokes, and the shape of a flow
- 3Switch, and branching honestly
- 4Loops over collections
- 5Local variables and assignment
- 6Sub-integrations and reuse
- 7Synchronous versus asynchronous
- 8Stitching in a database or file step
- 9When an orchestration is too big
- 10What breaks: three orchestration failures
- 11Lab briefing · Build a four-step flow