In IBM® Integration Bus, a SOAP message is described by a generic model that includes the SOAP Envelope and optionally Attachments. You define your SOAP message parts in a message map by using the Cast function.
A SOAP message consists of an Envelope and optionally Attachments. The envelope contains a SOAP header and a SOAP body. A SOAP body can include SOAP faults.
In IBM Integration Bus, when you use SOAP nodes, a SOAP message is described by a generic model.
In addition to the standard SOAP parts, the SOAP message generic model includes a Context part that includes contextual information about the current SOAP message that is processed. This part is the only one in a message map whose structure is included automatically. You must define the other SOAP message parts manually by using the Cast function.
The following table compares the SOAP message structure with the IBM Integration Bus SOAP message generic model:
Standard SOAP message parts | Status | IBM Integration Bus SOAP message parts | IBM Integration Bus Status |
---|---|---|---|
Context | Required | ||
SOAP header (part of the SOAP envelope) | Optional | Header (part of the SOAP_Domain_Msg) | Optional |
SOAP body (part of the SOAP envelope) | Required | Body (part of the SOAP_Domain_Msg) | Required |
SOAP faults (part of the SOAP body) | Optional | Fault (part of the Body) | Optional |
SOAP Attachments | Optional | Attachment (part of the SOAP_Domain_Msg) | Optional |
IBM Integration Bus supports SOAP 1.1 and SOAP 1.2 messages.
Message domain | Nodes usage | Schema to configure in a message map |
---|---|---|
SOAP | SOAP nodes without SOAPExtract
nodes Note: Applies when you transform a SOAP message within an message flow in an application
|
SOAP_Domain_Msg |
XMLNSC | SOAP nodes Note: Applies when you transform a SOAP message within an integration service operation
subflow
|
SOAP_Domain_Msg |
XMLNSC | SOAP nodes including the SOAPExtract node where the SOAPExtract node is modeled before the Mapping node | Schema associated with operation |
XMLNSC | Applications not using SOAP nodes, for example, HTTP nodes, MQ nodes, and FileInput nodes. | SOAP 1.1 or 1.2 schema as the root model of the map |
Complete the following steps to configure the SOAP_Domain_Msg when the Mapping node is connected directly from a SOAPInput node with no SOAPExtract node:
Define more transforms between the input SOAP_Domain_Msg and the output SOAP_Domain_Msg. For more information, see Specifying a transform (mapping operation).