Tasks
Automated migration with mixed version use
This migration approach also relies on the runtime migration tools provided by WAS ND. Like when using the Automated migration with whole node upgrade in the first step the existing WebSphere V5 / V6 configuration is recreated exactly in WebSphere Applications Server V7.0. After that, additional new WAS V7.0 nodes are added and apps can be migrated one by one when they are ready. As soon as all apps of an old node are migrated, the old node can be removed from the configuration.
This approach provides the following advantages and disadvantages:
Advantages
-- - There is no need for a self-written comprehensive set of scripts. All migration is performed using WAS tools.
-- - All the information in the current configuration is moved to WAS V7.0. Therefore, we do not have to worry about missing something.
-- - Allows more flexibility for app migration as migrations can be migrated when they are ready.
Disadvantages
-- - All the information of the current configuration is moved to WAS V7.0. The disadvantage of this approach is that we will also move configuration items that we no longer need.
-- - Care must be taken if we want to re-factor the topology during the migration phase.
-- - Manual enablement of some upgraded features is still required.