Oracle Integration Cloud: Building Integrations That Survive Production · Module 2 · The console and your first integration
Activation, and what it actually does
Lesson 16 of 175 · 2 min
An integration must be activated before it exists as far as anything outside OIC is concerned. Until then it is a design. WHAT CHANGES AT THAT MOMENT: the flow is deployed to the runtime, its endpoint is published, its schedule (if it has one) becomes live, and it starts appearing in monitoring. An unactivated integration cannot be called, cannot run on a schedule, and produces no instances — which is worth knowing because "my integration is not running" is a question with this as its first answer. AND THE ENDPOINT URL IS NOT STABLE UNTIL IT IS ACTIVATED, which matters more than it sounds. The URL embeds identifiers, so it is not something to hand to another team before the integration is live and its identifier settled — and identifiers are permanent, which is Lesson 6. Activation is also the moment a change becomes visible to callers, and that is…
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