Oracle Integration Cloud: Building Integrations That Survive Production · Module 7 · Scheduled integrations and file handling
The staging problem
Lesson 73 of 175 · 2 min
Where a file lives while being processed, and why MOVING IT BEFORE YOU FINISH is the difference between a safe rerun and a duplicate. The pattern is three directories: inbound, processing, and processed or error. A run claims a file by moving it out of inbound, works on it, and moves it to its final home when it is done. The location IS the state, and no separate register can drift from it. THE ORDER IS WHAT MATTERS AND IT IS COUNTERINTUITIVE. Move the file OUT of inbound BEFORE processing, so a second run — an overlap, a restart, somebody clicking twice — does not pick up the same file. Move it to processed only AFTER the work is committed, so a run that dies halfway leaves the file in the processing directory, visibly incomplete. THAT MIDDLE STATE IS THE POINT. A file sitting in processing after a failure is…
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