Oracle Integration Cloud: Building Integrations That Survive Production · Module 4 · The Fusion adapter in depth
Business objects versus services
Lesson 35 of 175 · 2 min
Two ways into the same data, with different shapes and different limits. Choosing deliberately rather than taking whichever appeared first is the lesson. BUSINESS OBJECTS are the modern, resource-shaped route. Nested children, a payload that looks like the thing it represents, and generated structures that are pleasant to map. Prefer them where they cover what you need. SERVICES are the older, operation-shaped route. Flatter, more verbose, and in some modules the only thing that exposes a particular operation. They also sometimes accept things the business object does not — a batch, a specific action, an option that never made it across. THE DIFFERENCES THAT ACTUALLY DECIDE IT. COVERAGE: if only one exposes the operation, that is the answer and there is no decision. SHAPE: a nested business object saves mapping work where your source is nested too, and costs it where your source is flat. LIMITS: paging behaviour, payload size…
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 4 · The Fusion adapter in depth
- 1What the Fusion adapter gives you
- 2Browsing the catalogue
- 3Business objects versus services
- 4Subscribing to a business event
- 5The service account and its roles
- 6Bulk operations and the file route
- 7Callbacks and long-running operations
- 8ERP integration patterns
- 9Reading a Fusion fault
- 10Surviving a Fusion quarterly update
- 11What breaks: five Fusion adapter failures
- 12Lab briefing · Read and write Fusion from OIC