Use the migration tools to migrate from a WebSphere Application
Server Network Deployment Version 5.x or 6.0.x deployment manager to a Version
6.1 deployment manager.
Before you begin
See Overview of migration, coexistence, and interoperability and Premigration considerations.
Mixed-version environment: Migrate the WebSphere Application Server Version 5.x or 6.0.x
deployment manager to Version 6.1 before migrating the managed nodes that
comprise the cell. The deployment manager must always be at the highest release
and fix level within a cell in order for it to manage all nodes in the cell.
In Version 6.1, the deployment manager can manage Version 5.x, Version 6.0.2,
and Version 6.1 release nodes. This allows a cell to be upgraded to a new
release one node at a time, with minimal impact to the applications that are
running within the cell. See
Coexistence support for information
on restrictions on using mixed-release cells.
mixv
Restriction: Migrating
to a Version 6.1 deployment manager on a remote machine is not supported.
For
help in troubleshooting problems when migrating, see Troubleshooting migration.
Tip: Before migrating a WebSphere Application Server Version 5.x or
6.0.x deployment manager, use the backupConfig command
or your own preferred backup utility to back up your existing configuration
if you want to be able to restore it to its previous state after migration.
Make sure that you note the exact name and location of this backed-up configuration.
Results
After the deployment manager is upgraded to Version 6.1, each node
in the cell can then be upgraded incrementally, one at a time. See Migrating to a Version 6.1 managed application server. The following diagram illustrates a mixed-release cell
containing a Version 6.1 deployment manager with both Version 5.x and Version
6.1 managed nodes:
