Oracle Integration Cloud: Building Integrations That Survive Production · Module 2 · The console and your first integration
Running it, and finding the instance
Lesson 17 of 175 · 2 min
Triggering a run and locating it in monitoring is THE single skill that makes everything after this debuggable. Every execution is an INSTANCE with its own identifier, and monitoring is a list of instances rather than a list of integrations. The mental shift is from "is my integration working" to "what did THIS run do", and every diagnostic question in this course is the second kind. What an instance shows you: when it ran, how it was triggered, whether it succeeded, which step it reached, and — the part that matters most — the payload at each point. Seeing what actually arrived, rather than what you believe was sent, resolves most mapping arguments in one look. Learn to FILTER before you need to. By integration, by time, by status. On a busy instance the default view is thousands of runs, and finding yours by scrolling is not a technique. Trigger…
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 2 · The console and your first integration
- 1The console, and the four places you will live
- 2Projects, and whether to use them
- 3Your first integration, start to finish
- 4Activation, and what it actually does
- 5Running it, and finding the instance
- 6Naming, and why it matters more than it should
- 7Versions and cloning
- 8What breaks: the first-week mistakes
- 9Lab briefing · Build, activate, run, find