Siebel Application Integration for Oracle Fusion Middleware Guide > Working with Web Services Using SAI for Oracle Fusion Middleware >

About Binding Options and Settings for Controlling the Structure of SOAP Messages

This topic describes the binding options and settings for controlling the structure of SOAP messages that are transmitted to and from a Siebel Web service.

SOAP Message Formats Supported in SAI for Oracle Fusion Middleware

SAI for Oracle Fusion Middleware supports both SOAP 1.1 and SOAP 1.2. SOAP 1.1 is based on XML 1.0 and can only use HTTP POST headers to transmit SOAP messages. Therefore, SOAP 1.1 is often not suitable for wide-scale applications. SOAP 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. SOAP 1.2 uses XML technologies to define an extensible messaging framework providing a message construct that you exchange over a variety of underlying protocols. The framework is designed to be independent of any particular programming model and other implementation-specific semantics.

SOAP Message Binding Options Supported in SAI for Oracle Fusion Middleware

A Web Services Description Language (WSDL) binding style can be either RPC or document. A WSDL describes a Web service by defining its interface, the operations on that interface, their binding to the transport protocol, and the network address where they are available. A WSDL binding describes how a Web service is bound to a messaging protocol, that is, what is the format or structure of the messages being exchanged with a service, and the transport protocol over which this message is sent. The most popular messaging protocol in Web services today is the SOAP messaging protocol. (The other option is to use REST-based messages.) The binding options supported in SAI for Oracle Fusion Middleware include Document/Literal and RPC/Literal.