The current WSIF default SOAP provider (the IBM Web Service SOAP provider) is designed to interoperate fully with a JAX-RPC compliant Web service, and therefore the current default provider does not fully interoperate with services that are running on the former (Apache SOAP) provider. To get your legacy services working again, you can either Modify your Web services to use the current IBM Web Service SOAP provider, or you can change the WSIF default provider back to Apache SOAP as described in this topic.
WSIF uses a properties file named wsif.properties to choose what SOAP provider to use. The SOAP provider is a node-wide setting, so all servers on the node must be restarted for any changes to take effect. The wsif.properties file is shipped in the wsif.jar file that is located in the install_root/lib directory (where install_root is the root directory for your installation of IBM WebSphere Application Server), and the "as shipped" properties file is accessed in this location by being put on the class path. However when you make changes to the file, you do not replace the original copy in the wsif.jar file. Instead, you save the modified version in the install_root/lib/properties directory.
To change the WSIF default SOAP provider back to Apache SOAP, complete the following steps:
# wsif.provider.default.org.apache.wsif.providers.soap.ApacheSOAP.WSIFDynamicProvider_ApacheSOAP=1 # wsif.provider.uri.1.org.apache.wsif.providers.soap.ApacheSOAP.WSIFDynamicProvider_ApacheSOAP=\ # http://schemas.xmlsoap.org/wsdl/soap/ #After the update, the preceding lines should look like this:
wsif.provider.default.org.apache.wsif.providers.soap.ApacheSOAP.WSIFDynamicProvider_ApacheSOAP=1 wsif.provider.uri.1.org.apache.wsif.providers.soap.ApacheSOAP.WSIFDynamicProvider_ApacheSOAP=\ http://schemas.xmlsoap.org/wsdl/soap/ #