Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Set up, enabling and migrating security
Migration and coexistence – Security considerations
Migration security configuration to new installation of WAS v8.0
- If security is enabled in the WAS v7 release, obtain the administrative server ID and password of the previous release. Optionally, disable security in the previous release before migrating the installation.
- WAS does not support the migration of security audit log files from the older release to v8.0. If there is a business need to preserve security audit logs from the older release, archive security audit log files in v7.x before migrating.
- If the WAS v7.x environment is enabled for Kerberos, and you are migrating to version 8.0 on a different machine, copy the Kerberos keytab and configuration files to the same location on the v8.0 machine.
- Start the First steps console...
cd WAS_HOME/profiles/profile_name/firststeps/
./firststeps.sh
- On the First steps console panel, click WebSphere Customization Toolbox.
- Open the Migration Management Tool.
- Follow the instructions provided to complete the migration.
- Migrate any custom class files that are not migrated.
Related
Interoperating with previous product versions
Interoperating with a C++ common object request broker architecture client
Migrate trust association interceptors
Migrate Common ORB Architecture programmatic login to JAAS (CORBA and JAAS)
Migrate from the CustomLoginServlet class to servlet filters
Migrate Java 2 security policy
Migrate with Tivoli Access Manager for authentication enabled on a single node
Migrate with Tivoli Access Manager for authentication enabled on multiple nodes
Migrate unrestricted jurisdiction policy files, local_policy.jar and US_export_policy.jar
JAAS
Web component security
Java EE connector security
Configure inbound identity mapping