Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 6 · Reports at scale: scheduling, delivery, performance
Delivery: email, FTP and content server
Lesson 57 of 177 · 2 min
Three channels, and what each does when the destination is down is the part that determines whether anyone notices a failure. EMAIL is per recipient and fails quietly. A wrong address bounces into a mailbox nobody reads, and the job status stays successful because handing the message to the mail system is all the job undertook. An email delivery that reports success is not evidence that anybody received anything. FTP or SFTP fails on the destination, the credential or the permission — and the dangerous case is the partial write, where the receiving system reads a file that is still being delivered. Write to a temporary name and rename on completion where the receiver supports it, or agree a marker file; both are the receiver's decision as much as yours, and both need agreeing before the first run rather than after the first bad file. THE CONTENT SERVER is the…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 6 · Reports at scale: scheduling, delivery, performance
- 1The scheduler, and what a job really is
- 2Scheduling patterns that survive
- 3Delivery: email, FTP and content server
- 4Knowing a scheduled report failed
- 5Volume: when the extract stops fitting
- 6Incremental extracts and high-water marks
- 7What breaks: the 2am report
- 8Lab briefing · Schedule, deliver, and prove it ran