Oracle Integration Cloud: Building Integrations That Survive Production · Module 3 · Connections and adapters
The FTP adapter
Lesson 26 of 175 · 2 min
Reading and writing files with a partner, and the three things that decide whether it works unattended. DIRECTORIES ARE THE STATUS. Inbound, processed, error — and moving a file between them is what records what has happened to it. The location IS the state, no separate register can drift from it, and an operator can see where everything stands without reading a log. PATTERNS are how you pick up the right files. A prefix, a date, an extension. Two rules make this safe: never match a pattern so broad it could pick up a file that is still being written, and agree the naming with the partner in writing, because it is their side that produces it. THE ARCHIVE STEP IS WHAT STOPS YOU PROCESSING YESTERDAY TWICE, and it is the one people leave out. A flow that reads the inbound directory and does not move what it read will…
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 3 · Connections and adapters
- 1What a connection is
- 2Choosing an adapterFree preview
- 3The REST adapter
- 4The SOAP adapter
- 5The FTP adapter
- 6The database adapter
- 7Testing a connection properly
- 8One connection or several
- 9Connectivity agents, and when you need one
- 10What breaks: four connection failures
- 11Lab briefing · Three connections, three systems