Migrating, coexisting, and interoperating – Security considerations


Use this topic to migrate the security configuration of previous WAS releases and its applications to the new installation of WAS.

This information addresses the need to migrate the security configurations from a previous release of IBM WAS to WAS 7.0 or later. Complete the following steps to migrate the security configurations:

 

Use the First steps wizard to access and run the Migration wizard.

  1. 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:

    • (Linux) [AIX] [HP-UX] [Solaris]

      (UNIX) ./APP_ROOT/profiles/profile_name/firststeps/firststeps.sh

    • (Windows) APP_ROOT\profiles\profile_name\firststeps\firststeps.bat

  2. On the First steps wizard panel, click Migration wizard.

  3. Follow the instructions provided in the First steps wizard to complete the migration.

 

Results

The security configuration of previous WAS releases and its applications are migrated to the new installation of WAS V7.0.

 

Next steps

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 standalone custom registry in the previous APP_ROOT/classes directory. Therefore, after migration, copy the custom user registry implementation classes to the APP_ROOT/classes directory.

If we upgrade from WAS, V5.x to WAS V7.0, the data that is associated with V5.x trust associations is not automatically migrated. To migrate trust associations, see Migrate trust association interceptors.


Interoperating with previous product versions
Interoperating with a C++ common object request broker architecture client
Migrate custom user registries
Migrate trust association interceptors
Migrate Common Object Request Broker Architecture programmatic login to (CORBA and JAAS)
Migrate from the CustomLoginServlet class to servlet filters
Migrate Java 2 security policy
Migrate with TAM for authentication enabled on a single node
Migrate with TAM for authentication enabled on multiple nodes

 

Related concepts


Java Authentication and Authorization Service
Web component security
J2EE connector security

 

Related tasks


Set inbound identity mapping