How Integration Server Determines the MEP Type to Use
Typically, the MEP type that an operation uses depends on whether its WSDL includes <wsdl:output> and/or <wsdl:fault> elements. A <wsdl:output> element defines the output a provider returns or that a consumer expects. A <wsdl:fault> element indicates whether a provider should respond with a fault or a consumer should expect a fault if an exception occurs. The table below summarizes the MEP type based on the WSDL for an operation.
<wsdl:output> element? | <wsdl:fault> element? | MEP Type |
Yes | Yes or No | In-Out MEP |
No | No | In-Only MEP |
No | Yes | Robust In-Only MEP |
For Integration Server MEP support, a web service descriptor’s Pre-8.2 compatibility mode property can alter the MEP type defined by the WSDL.
For provider web service descriptors, when the
Pre-8.2 compatibility mode property is
false,
Integration Server uses the MEP type based on the WSDL, as described in the table above. However, when the
Pre-8.2 compatibility mode property is
true,
Integration Server always uses In-Out MEP.
For consumer web service descriptors, the web service connector always expects responses based on the WSDL. For example, if the WSDL includes a
<wsdl:output> element, it expects a SOAP response. If the provider appropriately provides a response/fault based on the WSDL for the operation, the
Pre-8.2 compatibility mode property does not affect the behavior.
However, the
Pre-8.2 compatibility mode property does dictate how a web service connector reacts to receiving unexpected SOAP responses. When the
Pre-8.2 compatibility mode property is
false,
Integration Server ignores unexpected responses. When the
Pre-8.2 compatibility mode property is
true,
Integration Server honors unexpected responses. For more information, see
How <wsdl:output> and
<wsdl:fault> Elements Affect a Consumer.