MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 7 · Scheduled integrations and file handling

Lab briefing · A nightly file, done properly

Lesson 79 of 175 · 2 min

Build a scheduled file integration with staging, archiving and a missing-file alert — then KILL IT MID-RUN and prove the rerun is safe. The three structural pieces are the build. STAGING: inbound, processing, processed and error directories, with the file moved OUT of inbound before processing and into processed only after the work commits. ARCHIVING: files kept with a unique name so an operator can answer "what happened to Tuesday's". THE ALERT: a separate scheduled check that fires when nothing has been processed in the expected window. THEN KILL IT MID-RUN, and this is the whole point of the lab. Cancel the instance while it is halfway through a multi-record file. Then answer three questions before doing anything else. ONE: WHERE IS THE FILE? It should be in processing — claimed and unfinished, unambiguously. TWO: WHAT LANDED IN THE TARGET? Count the records actually created. That number is what 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.

See the course and enrol9 free lessons

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 7 · Scheduled integrations and file handling

  1. 1Scheduling an integration
  2. 2Parameters and run state
  3. 3Reading files: patterns and directories
  4. 4The staging problem
  5. 5Large files and chunking
  6. 6Writing files a partner can read
  7. 7Archiving and idempotent file processing
  8. 8Catching the file that never arrived
  9. 9What breaks: four file failures
  10. 10Lab briefing · A nightly file, done properly