WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Web services: when to use SOAP or HTTP nodes
HTTP and SOAP nodes can both be used to interact with Web services. Typically you use SOAP nodes when working with SOAP-based Web services.
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).
Cases where it might be better to use HTTP nodes include:
- Message flows in which a single request node handles multiple SOAP request and responses from more than one WSDL.
- Message flows that interact with Web services that use different standards, such as REST or XML-RPC.
- Message flow that never use WS-Addressing, WS-Security, SwA, or MTOM.