Oracle Integration Cloud: Building Integrations That Survive Production · Module 3 · Connections and adapters
The SOAP adapter
Lesson 25 of 175 · 2 min
Still necessary for parts of Fusion, which is the only reason this lesson exists — nobody chooses SOAP where REST is available. A WSDL describes the service completely: its operations, its message structures, its types. The adapter reads it and GENERATES the structures you map against, which is why SOAP integrations are verbose to look at and rarely ambiguous. THE GENERATION IS THE THING TO UNDERSTAND, because it is a SNAPSHOT. The structures in your integration were generated from the WSDL as it was when you configured the connection. If the service changes, your generated structures do not — and that gap is the source of the errors this lesson is named for. THE ERRORS THAT MEAN "YOUR WSDL IS STALE" RATHER THAN "YOUR CALL IS WRONG" look like validation failures: an element the service does not recognise, a type mismatch, a required element missing that your structure does not…
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 3 · Connections and adapters
- 1What a connection is
- 2Choosing an adapterFree preview
- 3The REST adapter
- 4The SOAP adapter
- 5The FTP adapter
- 6The database adapter
- 7Testing a connection properly
- 8One connection or several
- 9Connectivity agents, and when you need one
- 10What breaks: four connection failures
- 11Lab briefing · Three connections, three systems