Migrating JAX-RPC Web services security applications to Version 7.0 applications

Migration of a Java™ Platform, Enterprise Edition (Java EE) Version 1.3 application that uses Web services security to a Java EE Version 1.4 application is possible.

Before you begin

You can install Java Platform, Enterprise Edition (Java EE) Version 1.3 applications that use Web services security on a WebSphere® Application Server Version 7.0 server. However, if you want Java EE Version 1.3 applications to use the Web services security (WSS) Version 1.0 or 1.1 specifications and the other new features added in Version 7.0, you must migrate the Java EE Version 1.3 applications to Java EE Version 1.4.

About this task

Complete the following steps to migrate a Version 1.3 application, along with the Web services security configuration information, to a Version 7.0 application:

Procedure

  1. Save the original Java EE Version 1.3 application. You need the Web services 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 Platform, Enterprise Edition (Java EE) Migration Wizard in an assembly tool to migrate the Java EE Version 1.3 application to Java EE Version 1.4.
    Important: After you migrate to Java EE Version 1.4 using the Java EE Migration Wizard, you cannot view the Java EE Version 1.3 extension and binding information within an assembly tool. You can view the Java EE 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 Java EE Migration Wizard does not migrate the Web services security configuration files to the new format in the Java EE Version 1.4 application. Rather the wizard is used to migrate your files from Java EE Version 1.3 to Version 1.4.
    To access the Java EE Migration Wizard, complete the following steps:
    1. Right-click the name of your application.
    2. Click Migrate > Java EE 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 Java EE Version 1.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 Java EE Version 1.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 Web services security information in the new Version 7.0 format. For more information 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 Version 1.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 Java EE Version 1.3 application to a Java EE Version 1.4 application and specify this information using an assembly tool. 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 Java EE Version 1.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 JAX-RPC 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.



In this information ...


Related concepts

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 20, 2010 7:53:43 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-dist&topic=twbs_migratewssv6
File name: twbs_migratewssv6.html