Migrating Version 5.x applications with Web services security to Version 6 applications
You can install Java™ 2 Platform, Enterprise Edition (J2EE) Version 1.3 applications that use Web services security on a WebSphere® Application Server Version 6 server. However, if you want J2EE Version 1.3 applications to use the Web services security (WSS) Version 1.0 specification and the other new features added in Version 6, migrate the J2EE Version 1.3 applications to J2EE Version 1.4. This article provides general information about migrating a J2EE Version 1.3 application that uses Web services security to a J2EE Version 1.4 application.
Complete the following steps to migrate a Version 5.x application, along with the Web services security configuration information, to a Version 6 application:
- Save the original J2EE Version 1.3 application. You need the Web services security configuration files of the J2EE Version 1.3 application to recreate the configuration in the new format for the J2EE Version 1.4 application.
- Use the Java 2 Platform, Enterprise Edition (J2EE) Migration Wizard in an assembly tool to migrate the J2EE Version 1.3 application to J2EE Version 1.4.
Important: After you migrate to J2EE Version 1.4 using the J2EE Migration Wizard, you cannot view the J2EE Version 1.3 extension and binding information within an assembly tool. You can view the J2EE Version 1.3 Web services security extension and binding information using a text editor. However, do not edit the extension and binding information using a text editor. The J2EE Migration Wizard does not migrate the Web services security configuration files to the new format in the J2EE Version 1.4 application. Rather the wizard is used to migrate your files from J2EE Version 1.3 to Version 1.4. To access the J2EE Migration Wizard, complete the following steps:
- Right-click the name of your application.
- Click Migrate > J2EE Migration Wizard.
- Recreate the Web services security configuration information in the new J2EE Version 1.4 format. At this stage, because the application is already migrated to the J2EE Version 1.4, you can use the Application Server Toolkit to configure the original Web services security information in the new Version 6 format.
This task provides general information about how to migrate J2EE Version 1.3 applications to J2EE Version 1.4.
The following articles contain some general scenarios that map some of the basic Web services security information specified in a J2EE Version 1.3 application to a J2EE Version 1.4 application and specify this information using the Application Server Toolkit. The Web services security configuration information is contained in four configuration files: two server-side configuration files and two client-side configuration files. The migration of all of the configuration information is divided into four sections; one for each configuration file. When you recreate the Web services security information in the new J2EE Version 1.4 format, it is recommended that you configure the extensions and binding files in the following order:
- Configure the ibm-webservices-ext.xmi server-side extensions file. For more information, see Migrating the server-side extensions configuration.
- Configure the ibm-webservicesclient-ext.xmi client-side extensions file. For more information, see Migrating the client-side extensions configuration.
- Configure the ibm-webservices-bnd.xmi server-side bindings file. For more information, see Migrating the server-side bindings file.
- Configure the ibm-webservicesclient-bnd.xmi client-side bindings file. For more information, see Migrating the client-side bindings file.
- Migrating the server-side extensions configuration
- Migrating the client-side extensions configuration
- Migrating the server-side bindings file
- Migrating the client-side bindings file
- View Web services client deployment descriptor
Use this page to view your client deployment descriptor.- View Web services server deployment descriptor
Use this page to view your server deployment descriptor settings.