Oracle Integration Cloud: Building Integrations That Survive Production · Module 18 · Capstone: one integration, delivered
The brief
Lesson 170 of 175 · 3 min
A partner file, a Fusion target, a schedule, and TWO CONSTRAINTS THAT MAKE THE OBVIOUS DESIGN WRONG. The brief is deliberately ordinary. A partner drops a file on an SFTP server each night. It has to reach Fusion. Somebody will ask you what happened to a particular record. That is most of the integration work in this market, and every module in this course applies to it. THE OBVIOUS DESIGN IS ALSO OBVIOUS: a scheduled integration that collects the file, maps each row, and calls Fusion per record. It works, it is quick to build, and it is what most people produce. Two constraints in the brief make it the wrong answer, and finding out which two before you build is the point of the module. THE FIRST IS VOLUME. The file is far larger than the sample you were sent, and the window is fixed. Per-record calls do not…
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.