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 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.
IBM Integration Bus supports SOAP 1.1 and SOAP 1.2 messages.
Message domain | Nodes usage | Schema to configure in a message map |
---|---|---|
XMLNSC | All SOAP nodes within an integration service operation subflow. | Schema for operation request or response. |
XMLNSC | SOAPInput nodes in flows that have a SOAPExtract node before the Mapping node. | Schema for operation request. |
XMLNSC | SOAPReply or SOAPRequest nodes that might be preceded in a flow by a SOAPEnvelope node. | Schema for operation request or response. |
SOAP | SOAPInput nodes that are wired directly to the Mapping node. | IBM-provided SOAP_Env where the body xsd:any has a mapping cast to the schema for the operation request. |
SOAP | SOAPReply or SOAPRequest nodes that are wired directly to the Mapping node. | IBM-provided SOAP_Env where the body xsd:any has a mapping cast to the schema for the operation request or response. |
XMLNSC | Flows that do not contain SOAP nodes. For example, flows that contain HTTP nodes, MQ nodes, or FileInput nodes. | IBM-provided SOAP 1.1 or SOAP 1.2 schema where the body xsd:any has a mapping cast to the schema for the operation request or response. |
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 |
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).