Migrating Web services

If you are migrating your Web service or Web service components from earlier versions of WebSphere® Studio, there are several hints and tips that will improve your success.

Migration hints

  • For any IBM® SOAP-based Web service related projects generated using WebSphere Studio v5.x, the libraries in your build paths may point to JAR files which no longer exist in their old location. Most of the JAR files were in the following plugins:
    • com.ibm.etools.webservice
    • com.ibm.etools.webservice.ui
    The JAR files are now in com.ibm.etools.webservice.consumption.soap.
  • In order to migrate EJB and EAR projects from WebSphere Studio Application Developer Integration Edition to one of the Rational® Developer products, you should import the project from your existing workspace. Using other methods to migrate projects is discouraged as project meta information may not be maintained which results in WSDL validation errors.
  • Secure Web services are not migrated by the J2EE Migration Wizard when Web services are migrated from J2EE 1.3 to J2EE 1.4. The migration of secure Web services requires manual steps. After the J2EE migration, the secure binding and extension files must be migrated manually to J2EE 1.4 as follows:
    1. Double click on the webservices.xml file to open the Web Services editor.
    2. Select the Binding Configurations tab to edit the binding file.
    3. Add all the necessary binding configurations under the new sections Request Consumer Binding Configuration Details and Response Generator Binding Configuration Details.
    4. Select the Extension tab to edit the extension file.
    5. Add all the necessary extension configurations under the new sections Request Consumer Service Configuration Details and Response Generator Service Configuration Details.
    6. Save and exit the editor.
Terms of use | Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.