This topic presents best practices when migrating Web services applications.
Migrating a Version 5 JAX-RPC client that uses SOAP over JMS to invoke a Web service
A Java API for XML-based remote procedure call (JAX-RPC) client running on WebSphere Application Server Version 5, can use SOAP over Java Messaging Service to invoke a Web service that is running on a Version 5 application server.
SibMessage W [:] CWSIT0009W: A client request failed in the application server with endpoint <endpoint name> in bus <bus_name> with reason: CWSIT0016E: The user ID null failed authentication in bus <bus_name>.When the application server is migrated to Version 6, and the default messaging provider (service integration technologies) is used, and global security is enabled for the server or the cell, the service integration bus queue destination inherits the security characteristics of the server or the cell by default. If the server or the cell has basic authentication enabled, the client request fails.
Migrating Apache SOAP Web services
See Migrating Apache SOAP Web services to Web Services for J2EE standards to learn how to migrate Apache SOAP Web services. This topic explains how to migrate Web services that were developed using Apache SOAP to Web services that are developed based on the Web Services for Java 2 Platform, Enterprise Edition (J2EE) specification.
Migrating Web services assembled with early versions of the Application Server Toolkit or Assembly Toolkit