Oracle Integration Cloud: Building Integrations That Survive Production · Module 2 · The console and your first integration
Projects, and whether to use them
Lesson 14 of 175 · 2 min
The newer grouping model. A project holds integrations, connections and lookups together as a unit, and that changes three things: ownership, deployment and naming. OWNERSHIP. A project is a boundary somebody can be responsible for. In an estate with several teams, that is worth a great deal: it answers "whose is this" without a naming convention doing the work. DEPLOYMENT. A project moves between environments as a unit rather than as a list of individually promoted artefacts. That is the strongest argument for projects, and it matters most where promotion is frequent — which is Module 16. NAMING. Grouping absorbs part of what a naming convention was carrying, so identifiers can be shorter and more readable. WHEN IT HELPS: several teams, several environments, more than a handful of integrations, and a promotion path you use regularly. WHEN IT ADDS A LAYER TO A TWO-INTEGRATION ESTATE: exactly that — a client…
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