Linking a WSIF service to a SOAP over HTTP service

The SOAP provider allows WSIF stubs and dynamic clients to invoke SOAP services. Add Web Services Description Language (WSDL) extensions to your web service WSDL file so that the service can use the SOAP provider.

Before you begin

Note: The current WSIF default SOAP provider (the IBM® Web Service SOAP provider) does not fully interoperate with services that are running on the former (Apache SOAP) provider. This is because the IBM Web Service SOAP provider is designed to interoperate fully with a JAX-RPC compliant web service, and Apache SOAP cannot provide such a service. For more information see WSIF SOAP provider: working with existing applications.

About this task

The Web Services Invocation Framework (WSIF) SOAP provider supports SOAP 1.1 over HTTP.

The SOAP provider is JSR 101/109 compliant and uses Web Services for Java™ EE for parsing and creating SOAP messages.

The SOAP provider supports:

  • SOAP-ENC encoding.
  • RPC style and Document style SOAP messages.
  • SOAP messages with attachments.

The SOAP provider is not transactional.

The SOAP provider does not support the WSIF synchronous timeout. The SOAP provider uses the default client timeout value that is set for Web Services for Java EE.

To link a WSIF service to a SOAP over HTTP service, you write extensions to the service WSDL file.

Procedure


Icon that indicates the type of topic Task topic



Timestamp icon Last updated: March 5, 2017 17:29
File name: twsf_prs.html