+

Search Tips   |   Advanced Search

 

Migrating V5.x applications with Web services security to V6.1 applications

 

Migration of a J2EE Version 1.3 application that uses Web services security to a Java 2 Platform, Enterprise Edition V1.4 application is possible.

You can install Java 2 Platform, Enterprise Edition Version 1.3 applications that use Web services security on a WebSphere Application Server V6.1 server. However, if you want J2EE V1.3 applications to use the Web services security (WSS) V1.0 specification and the other new features added in V6.1, migrate the J2EE V1.3 applications to J2EE V1.4.

 

Overview

Complete the following steps to migrate a V5.x application, along with the Web services security configuration information, to a V6.1 application:

 

Procedure

  1. Save the original J2EE V1.3 application. We need the Web services security configuration files of the J2EE V1.3 application to recreate the configuration in the new format for the J2EE Version 1.4 application.

  2. Use the J2EE Migration Wizard in an assembly tool to migrate the J2EE V1.3 application to J2EE Version 1.4.

    After you migrate to J2EE V1.4 using the J2EE Migration Wizard, you cannot view the J2EE V1.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 V1.4 application. Rather the wizard is used to migrate your files from J2EE V1.3 to V1.4. To access the J2EE Migration Wizard...

    1. Right-click the name of your application.

    2. Click Migrate > J2EE Migration Wizard.

  3. Manually delete all of the Web services security configuration information from the binding and extension files of the application that is migrated to J2EE V1.4.

    1. Delete the <securityRequestReceiverServiceConfig> and <securityResponseSenderServiceConfig> sections from the server-side ibm-webservices-ext.xmi extension file.

    2. Delete the <securityRequestReceiverBindingConfig> and <securityResponseSenderBindingConfig> sections from the server-side ibm-webservices-bnd.xmi binding file.

    3. Delete the <securityRequestSenderServiceConfig> and <securityResponseReceiverServiceConfig> sections from the client-side ibm-webservicesclient-ext.xmi extension file.

    4. Delete the <securityRequestSenderBindingConfig> and <securityResponseReceiverBindingConfig> sections from client-side ibm-webservicesclient-bnd.xmi binding file.

  4. Recreate the Web services security configuration information in the new J2EE V1.4 format. At this stage, because the application is already migrated to the J2EE V1.4, you can use the Application Server Toolkit to configure the original Web services security information in the new V6.1 format.

 

Results

This task provides general information about how to migrate J2EE Version 1.3 applications to J2EE V1.4.

 

What to do next

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 V1.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 V1.4 format, it is recommended that you configure the extensions and binding files in the following order:

  1. Configure the ibm-webservices-ext.xmi server-side extensions file. For more information, see Migrating the server-side extensions configuration.

  2. Configure the ibm-webservicesclient-ext.xmi client-side extensions file. For more information, see Migrating the client-side extensions configuration.

  3. Configure the ibm-webservices-bnd.xmi server-side bindings file. For more information, see Migrating the server-side bindings file.

  4. 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

View Web services server deployment descriptor

 

Related tasks


Securing Web services applications using JAX-RPC at the message level