MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 10 · Business events and publish/subscribe

Lab briefing · Subscribe, drop, and catch up

Lesson 109 of 175 · 2 min

Subscribe to a Fusion event, DEACTIVATE the integration, raise three events, then REACTIVATE and account for all three. "Account for all three" is the exercise, and the answer is not known in advance. Depending on the mechanism you may get all three, one, or none — and finding out which, for your subscription in your instance, is the point. First, prove the event fires at all, per Lesson 2: subscribe, do the thing in Fusion, confirm an instance. Do not skip this; an experiment that starts with an event that never fires produces a very confident wrong conclusion about deactivation. Then deactivate and raise three events, distinguishable from each other — three different records, so you can tell exactly which arrived. Reactivate and count. THREE: they were queued, and you have a stronger guarantee than you assumed. ZERO: they are gone, and every deactivation is a data gap. ONE OR

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.

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 10 · Business events and publish/subscribe

  1. 1Event-driven versus polling
  2. 2Fusion business events, in practice
  3. 3Subscribing without losing events
  4. 4Ordering, and why you cannot rely on it
  5. 5At-least-once delivery
  6. 6OIC events between integrations
  7. 7What breaks: three event failures
  8. 8Lab briefing · Subscribe, drop, and catch up