Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web services - Invocation framework (WSIF) > Use WSIF to invoke web services > Link a WSIF service to the underlying implementation of the service
Link a WSIF service to a SOAP over HTTP service
The SOAP provider allows WSIF stubs and dynamic clients to invoke SOAP services. Add WSDL extensions to your web service WSDL file so that the service can use the SOAP provider.
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.
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
- Optional: If we have a web service that you expect multiple clients to use to connect over SOAP, before you deploy the service set up your application deployment descriptor file dds.xml to handle multiple connections. See the troubleshooting tip Use WSIF with multiple clients causes a SOAP parsing error.
- Write the WSDL extension that lets your WSIF service access a SOAP over JMS service.
The WSDL binding extension for SOAP over JMS varies only slightly from the SOAP over HTTP binding.
- Write the WSDL extensions for SOAP attachments.
Related
WSIF SOAP provider: working with existing applications
Link a WSIF service to a JMS-provided service
Write the WSDL extension that lets your WSIF service invoke a method on a local Java object
Write the WSDL extension that lets your WSIF service invoke an enterprise bean
WSIFOperation - Synchronous and asynchronous timeouts reference
Plan to use web services
Example: Passing SOAP messages with attachments by using WSIF
Link a WSIF service to the underlying implementation of the service