Modifying Web services to use the IBM Web Service SOAP provider

The current WSIF default SOAP provider (the IBM Web Service SOAP provider) is designed to interoperate fully with a JAX-RPC compliant Web service, 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 as described in this topic or you can change the WSIF default provider back to Apache SOAP.

To modify a legacy Web service, use WebSphere Studio Development Client for iSeries to complete the following steps and thereby generate new deployment artifacts for access to the service from the IBM Web Service provider:

1. Import into the Workspace the project that contains your legacy Web services.
2. For every legacy SOAP service in the project, repeat the following steps:
   1. From the pop-up menu for yourService.wsdl, select Generate Deploy Code.
   2. In the Generate Deploy Code window, change the Inbound Binding Type from SOAP to IBM Web Service then click Finish.
3. Export the EAR file that contains all of the deployment artifacts for the IBM Web Service Web service.