Migrate Web Services Security-enabled JAX-RPC applications from Java EE Version 1.3 to Version 1.4

We can migrate a JAX-RPC Java EE Version 1.3 application that uses Web Services Security (WSS) to Java EE Version 1.4. JAX-RPC Java EE Version 1.3 applications are supported on WebSphere Application Server Version 5 and later. JAX-RPC Java EE Version 1.4 applications are supported on WAS v6 and later.

WAS v6 and later supports both JAX-RPC Java EE Version 1.3 and Java EE Version 1.4 applications. JAX-RPC Java EE Version 1.3 applications use the WSS Draft 13 specification, and JAX-RPC Java EE 1.4 applications use the WSS 1.0 specification. If we want the JAX-RPC Java EE Version 1.3 application to use the WSS 1.0 or 1.1 specifications, migrate the application to Java EE 1.4. For more information on the compatibility of applications that use WSS Draft 13 and WSS 1.0, see Overview of standards and programming models for web services message-level security.

Complete the following steps to migrate a JAX-RPC Java EE Version 1.3 application, along with the Web Services Security configuration information, to a Java EE Version 1.4 application:

  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 re-create 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 Version 1.4.

    Important: After you migrate to Java EE Version 1.4 using the Java EE Migration Wizard, we cannot view the Java EE Version 1.3 extension and binding information within an assembly tool. We 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 the files from Java EE Version 1.3 to Version 1.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 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. Re-create 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 WSS 1.0 format. For more information on assembly tools, see the related information.


Results

You migrated a JAX-RPC Java EE Version 1.3 application 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 re-create the Web Services Security information in the new Java EE Version 1.4 format, IBM recommends configured the extensions and binding files in the following order:

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

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

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

  4. Configure the ibm-webservicesclient-bnd.xmi client-side bindings file. For more information, see Migrate the client-side bindings file.


Subtopics


Related concepts

  • Development and assembly tools
  • Overview of standards and programming models for web services message-level security