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 8.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 8.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 8.0 application:
Procedure
- 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.
- 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:
- Right-click the name of your application.
- Click .
- 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.
- Delete the <securityRequestReceiverServiceConfig> and <securityResponseSenderServiceConfig> sections
from the server-side ibm-webservices-ext.xmi extension
file.
- Delete the <securityRequestReceiverBindingConfig> and <securityResponseSenderBindingConfig> sections
from the server-side ibm-webservices-bnd.xmi binding
file.
- Delete the <securityRequestSenderServiceConfig> and <securityResponseReceiverServiceConfig> sections
from the client-side ibm-webservicesclient-ext.xmi extension
file.
- Delete the <securityRequestSenderBindingConfig> and
<securityResponseReceiverBindingConfig> sections
from client-side ibm-webservicesclient-bnd.xmi binding
file.
- 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 8.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:
- Configure the ibm-webservices-ext.xmi server-side
extensions file. For more information, see Migrating the JAX-RPC 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.