Migrating security configurations from previous releases
Migrating, coexisting, and interoperating - Security considerations
Use this topic to migrate the security configuration of previous WebSphere Application Server releases and its applications to the new installation of WebSphere Application Server.
This information addresses the need to migrate your security configurations from a previous release of IBM WebSphere Application Server to WebSphere Application Server Version 6.0.x or later. Complete the following steps to migrate your security configurations:
If security is enabled in the previous release, obtain the administrative server ID and password of the previous release. This information is needed in order to run certain migration jobs.
You can optionally disable security in the previous release before migrating the installation. No logon is required during the installation.
Use the First steps wizard to access and run the
Migration wizard.
Start the First steps wizard by launching the firststeps.bat or the firststeps.sh file. The first steps file is located in the following directory:
The security configuration of previous WebSphere Application Server releases and its applications are migrated to the new installation of WebSphere Application Server Version 6.0.x.
What to do next
If a custom user registry is used in the previous version, the migration process does not migrate the class files that are used by the custom user registry in the previous_install_root/classes directory.
Therefore, after migration, copy your custom user registry implementation classes to the install_root/classes directory.
If you upgrade from WebSphere Application Server, Version 5.x to WebSphere Application Server, Version 6.0.x, the data that is associated with Version 5.x trust associations is not automatically migrated to Version 6.0.x. To migrate trust associations, see Migrating trust association interceptors
.