You can configure message flows that include the HTTP
or SOAP nodes to access the HTTP transport to work with the following
resources:
- SOAP-based web services
- Other web services standards, such as REST or XML-RPC
- General HTTP messaging, where the payload might be XML
HTTP nodes can process non-secure (HTTP) messages and secure
(HTTPS or HTTP over SSL) messages.
For SOAP-based web services, several advantages
exist if you use the SOAP nodes and the SOAP message domain instead
of the HTTP transport nodes and XMLNSC message domain.
- Support for WS-Addressing, WS-Security and SOAP headers.
- A common SOAP logical tree format, independent of the bitstream
format.
- Runtime checking against WSDL.
- Automatic processing of SOAP with Attachments (SwA).
- Automatic processing of Message Transmission Optimization Mechanism
(MTOM).
Although the HTTP nodes can process SwA messages, you must use
the MIME message domain and design your flow to handle the attachments
explicitly, and use custom logic to extract and parse the SOAP.
For more
information about using SOAP messages and message flow nodes, see What is SOAP?
For more information about using the
WebSphere® Broker
HTTP Transport, see the following topics: