Binders

Multiple binders with different operations

In pre-8.2 compatibility mode, Integration Server permits a single web service descriptor to contain multiple binders with different operations.

When not in pre-8.2 compatibility mode, all the binders for a single web service descriptor must contain the same operations. Integration Server will not save a service first provider web service descriptor if it contains multiple binders that list different operations.

Binding Styles

Mixed binding styles in web service descriptors

In pre-8.2 compatibility mode, Integration Server does not restrict the binding styles in a web service descriptor. A web service descriptor could contain binders that used different binding styles.

When not in pre-8.2 compatibility mode, Integration Server requires all binders within a web service descriptor to use the same binding style. That is, all the binders in a single web service descriptor should specify a binding style of RPC or Document for all of the binders.

Binding Styles

Mixed binding styles in WSDLs

In pre-8.2 compatibility mode, Integration Server creates web service descriptors from WSDLs that contained bindings that used different binding styles.

When not in pre-8.2 compatibility mode, Integration Server requires all bindings in the consumed WSDL to have the same style. Integration Server will not create a web service descriptor from a WSDL that contains mixed styles across its bindings.

JMS Bindings

Support for JMS bindings and JMS binders

In pre-8.2 compatibility mode, Integration Server supports HTTP and HTTPS bindings only.

When not in pre-8.2 compatibility mode, Integration Server supports JMS bindings in addition to HTTP and HTTPS bindings.

Message Exchange Pattern (MEP) Support

Added In-Only MEP and Robust In-Only MEP support

In pre-8.2 compatibility mode, Integration Server supports only In-Out MEP for web service operations.

When not in pre-8.2 compatibility mode, Integration Server supports In-Only MEP and Robust In-Only MEP, in addition to In-Out MEP.

MTOM Attachments

Streaming MTOM Attachments

In Pre-8.2 compatibility mode, Integration Server supports MTOM attachments in both inbound and outbound messages. However, Integration Server cannot stream the MTOM attachments. Integration Server always holds the MTOM attachment in memory.

When not in Pre-8.2 compatibility mode, Integration Server can stream the MTOM attachments for both inbound and outbound SOAP messages.

Port types

Port types in web service descriptors

In pre-8.2 compatibility mode, Integration Server supports multiple port types. When Integration Server generated a WSDL for a multi-binder web service descriptor, the resulting WSDL had multiple port types.

When not in pre-8.2 compatibility mode, Integration Server does not support multiple port types. As a result, when Integration Server generates a WSDL for a multi-binder provider web service descriptor, it changes the port type names so that the generated WSDL has only a single port type.

Port types

Port types in WSDLs

In pre-8.2 compatibility mode, Integration Server creates web service descriptors from WSDLs that contained multiple port types.

When not in pre-8.2 compatibility mode, Integration Server does not support creating web service descriptors from WSDLs that contain multiple port types.

Provider web service descriptor

Provider web service descriptor with no operations

In pre-8.2 compatibility mode, Integration Server permits a provider web service descriptor that does not contain any operations.

When not in pre-8.2 compatibility mode, Designer will not save a web service descriptor if it does not contain at least one operation.

Response services

Response services in consumer web service descriptor

In pre-8.2 compatibility mode, Integration Server does not create the responseServices folder when creating a consumer web service descriptor.

When not in pre-8.2 compatibility mode, Integration Server creates the responseServices folder that contains response services for each operation in the WSDL document and a genericFault_Response service when creating a consumer web service descriptor.

Service name

Name attribute in wsdl:service element

In pre-8.2 compatibility mode, the local name of the web service descriptor determines the value of the name attribute in the wsdl:service element in the associated WSDL document. For example, suppose that a web service descriptor has the fully qualified name folder.myFolder:myWebService. In the WSDL document, the value of the name attribute in the wsdl:service element is "myWebService".

When not in pre-8.2 compatibility mode, the fully qualified name of the web service descriptor determines the value of the name attribute in the wsdl:service element. For example, suppose that a web service descriptor has the fully qualified name folder.myFolder:myWebService. In the WSDL document, the value of the name attribute in the wsdl:service element is "folder.myFolder:myWebService".

Web service handlers

Web service handlers based on JAX-RPC

In pre-8.2 compatibility mode, Integration Server supports web service handlers based on JAX-RPC.

When not in pre-8.2 compatibility mode, Integration Server will not execute web service handlers based on JAX-RPC.

Web service handlers

Web service handler chain execution

In pre-8.2 compatibility mode, you can use the WS-Security facility to secure a web service. The WS-Security facility secures web services using the WS-Security handler. Because a handler is used, Integration Server can perform additional processing before and after the security processing. That is, for inbound messages Integration Server can invoke handlers before invoking the WS-Security handler to perform security processing. For outbound messages, Integration Server can invoke custom handlers after it invokes the WS-Security handler, but before it sends the outbound message. The order of the handlers on the Handlers tab determines the order in which Integration Server invokes them.

When not in pre-8.2 compatibility mode, for inbound messages, Integration Server always performs the security processing first upon receiving the message. As a result, Integration Server cannot invoke custom handlers before the security processing of an inbound message. For outbound messages, Integration Server always performs the security processing last, right before it sends the message. As a result, Integration Server cannot invoke handlers after the security processing of an outbound message.

WS-Addressing

WS-Addressing

In pre-8.2 compatibility mode, Integration Server does not support WS-Addressing.

When not in pre-8.2 compatibility mode, Integration Server implements WS-Addressing by associating WS-Addressing policies that conform to Web Services Policy framework to web service descriptors.

WS-Policy

WS-Policy

In pre-8.2 compatibility mode, Integration Server does not support WS-Policy.

When not in pre-8.2 compatibility mode, Integration Server supports the WS-Policy framework.

WS-Security

WS-Security facility

In pre-8.2 compatibility mode, Integration Server implemented WS-Security by associating WS-Security handlers to web service descriptors.

When not in pre-8.2 compatibility mode, Integration Server implements WS-Security by associating WS-Security policies that conform to Web Services Policy framework to web service descriptors.