Oracle Integration Cloud: Building Integrations That Survive Production · Module 7 · Scheduled integrations and file handling
Reading files: patterns and directories
Lesson 72 of 175 · 2 min
Matching the files you meant, ignoring the ones you did not, and THE WILDCARD THAT PICKED UP A PARTNER ARCHIVE FOLDER. A pattern decides which files the run takes, and the failure mode is that it is either too narrow (nothing processes and nobody is told) or too broad (something processes that should not have). THE ARCHIVE FOLDER STORY IS THE CANONICAL TOO-BROAD FAILURE. The partner keeps a year of history beside the current file — entirely reasonably — and a pattern matching everything with the right extension picks up all of it. The run succeeds, processes four hundred old files, and creates a year of duplicate records, which is a data cleanup rather than a rerun. So: match as SPECIFICALLY as the naming allows — a prefix and a date pattern, not just an extension — and read from a directory that contains only what is to be processed.…
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