This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Binding style

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
The binding style specifies how a service is bound to a messaging protocol, particularly the SOAP protocol. Binding style is also referred to as the WSDL style or encoding style.

There are several binding styles, however, they are divided into two categories. Document style, which sends the entire XML document in a message, and Remote Procedure Call (RPC), which sends part of a message. These categories are themselves divided into subcategories, which are explained in detail in Which WSDL style should I use? External link opens a new window or tab. There are tradeoffs to each one. The default selection in the interface editor, document literal wrapped, is sufficient for most uses. However, if you are using an attachment in a business object, document literal non-wrapped must be used.

If you bring an interface into the interface editor and another binding style has been used then the editor will leave the binding style as it is. This feature is known as toleration. The following binding styles are supported by the interface editor:

Table 1. Binding styles in the interface editor
Binding style Interface editor support
Document literal wrapped Default
Document literal non-wrapped (used with attachments) Can be selected from the interface editor
Remote Procedure Call (RPC) Tolerated if WSDL has been imported
Unknown Tolerated if WSDL has been imported