+

Search Tips   |   Advanced Search

Migrate JAX-RPC WS-Security applications to V7.0 applications


Migration of a Java EE Version 1.3 application that uses WS-Security to a Java EE Version 1.4 application is possible.

We can install Java EE Version 1.3 applications that use WS-Security on a WAS V7.0 server. However, if we want Java EE V1.3 applications to use the Web services security (WSS) V1.0 or 1.1 specifications and the other new features added in V7.0, migrate the Java EE Version 1.3 applications to Java EE V1.4.

Complete the following steps to migrate a V1.3 application, along with the WS-Security configuration information, to a V7.0 application:

 

  1. Save the original Java EE V1.3 application. You need the WS-Security configuration files of the Java EE Version 1.3 application to recreate the configuration in the new format for the Java EE Version 1.4 application.

  2. Use the Java EE Migration Wizard in an assembly tool to migrate the Java EE Version 1.3 application to Java EE V1.4.

    After you migrate to Java EE V1.4 using the Java EE Migration Wizard, we cannot view the Java EE V1.3 extension and binding information within an assembly tool. We can view the Java EE Version 1.3 WS-Security extension and binding information using a text editor. However, do not edit the extension and binding information using a text editor. The Java EE Migration Wizard does not migrate the WS-Security configuration files to the new format in the Java EE Version 1.4 application. Rather the wizard is used to migrate the files from Java EE Version 1.3 to V1.4.

    To access the Java EE Migration Wizard...

    1. Right-click the name of the application.

    2. Click Migrate > Java EE Migration Wizard.

  3. Manually delete all of the WS-Security configuration information from the binding and extension files of the application that is migrated to Java EE 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 WS-Security configuration information in the new Java EE V1.4 format. At this stage, because the application is already migrated to the Java EE Version 1.4, use an assembly tool to configure the original WS-Security information in the new V7.0 format.

    See on assembly tools, see the related information.

 

Results

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

 

Next steps

The following articles contain some general scenarios that map some of the basic WS-Security information specified in a Java EE Version 1.3 application to a Java EE V1.4 application and specify this information using an assembly tool. The WS-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 WS-Security information in the new Java EE Version 1.4 format, it is recommended that you configure the extensions and binding files in the following order:

  1. Set the ibm-webservices-ext.xmi server-side extensions file.

    See Migrate the JAX-RPC server-side extensions configuration.

  2. Set the ibm-webservicesclient-ext.xmi client-side extensions file.

    See Migrate the client-side extensions configuration.

  3. Set the ibm-webservices-bnd.xmi server-side bindings file.

    See Migrate the server-side bindings file.

  4. Set the ibm-webservicesclient-bnd.xmi client-side bindings file.

    See Migrate the client-side bindings file.


Migrate the JAX-RPC server-side extensions configuration
Migrate the client-side extensions configuration
Migrate the server-side bindings file
Migrate the client-side bindings file
View Web services client deployment descriptor
View Web services server deployment descriptor

 

Related concepts


Assembly tools

 

Related tasks


Secure JAX-RPC Web services using message level security