Oracle Integration Cloud: Building Integrations That Survive Production · Module 7 · Scheduled integrations and file handling
Parameters and run state
Lesson 71 of 175 · 2 min
Passing values into a scheduled run, and keeping a HIGH-WATER MARK between runs so the next one knows where the last stopped. Parameters on a scheduled integration are set on the schedule rather than by a caller, and the date trap from the Technical course applies exactly: a parameter defaulting to "today" means something different at 00:05 on the first of the month than it did when you tested it at eleven in the morning. Express dates RELATIVE to the run. RUN STATE is what makes an incremental flow possible: a value the run reads at the start and writes at the end, so the next run picks up where this one stopped. THE THREE RULES THAT MAKE A HIGH-WATER MARK SAFE. BASE IT ON A TIMESTAMP THE SOURCE SETS, not on the run time — the run clock and the data clock are different, and using the wrong one…
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 7 · Scheduled integrations and file handling
- 1Scheduling an integration
- 2Parameters and run state
- 3Reading files: patterns and directories
- 4The staging problem
- 5Large files and chunking
- 6Writing files a partner can read
- 7Archiving and idempotent file processing
- 8Catching the file that never arrived
- 9What breaks: four file failures
- 10Lab briefing · A nightly file, done properly