Migrate security configurations from previous releases
Before you beginThis article addresses the need to migrate your security configurations from a previous release of IBM WAS to WebSphere Application Server V6. Complete the following steps to migrate your security configurations:
- Before migrating your configurations, verify that the administrative server of the previous release is running.
- If security is enabled in the previous release, obtain the server ID and password of the previous release. This information is needed to log onto the administrative server of the previous release during migration.
- You can optionally disable security in the previous release before migrating the installation. There is no logon required during the installation.
- Start the First steps wizard by launching the firststeps.bat or firststeps.sh file. The first steps file is located in the following directory:
- On the First steps wizard panel, click Migration wizard.
- Follow the instructions provided in the First steps wizard to complete the migration.
For more information on the Migration wizard, see Using the Migration wizard.
ResultThe security configuration of previous WebSphere Application Server releases and its applications are migrated to the new installation of WAS V6.
What to do nextThis task is for migrating an installation.
If a custom user registry is used in the previous version, the migration process does not migrate the class files 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, V5.x or 4.0.x to WebSphere Application Server, v6.x, the data that is associated with V5.x or 4.0.x trust associations is not automatically migrated to v6.x. To migrate trust associations, see Migrating trust association interceptors.
Migrating custom user registries
Migrating trust association interceptors
Migrating Common Object Request Broker Architecture programmatic login to Java Authentication and Authorization Service
Migrating from the CustomLoginServlet class to servlet filters
J2EE Connector security
Custom user registries
Java Authentication and Authorization Service
Web component security
Installing the product and additional software
Configuring inbound identity mapping
Using the Migration wizard
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.