WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results

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, 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 as described in this topic, or you can change the WSIF default provider back to Apache SOAP.

About this task

To modify a legacy Web service, use the assembly tool to complete the following steps and thereby generate new deployment artifacts for access to the service from the IBM Web Service provider:

Procedure

  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 your_service.wsdl, select Generate Deploy Code.
    2. In the Generate Deploy Code window, change the Inbound Binding Type from SOAP to IBM Web Service.
    3. Click Finish.
  3. Export the EAR file that contains all of the deployment artifacts for the IBM Web Service Web service.



In this information ...


IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/twsf_soap_io_chws.html