Use the migration tools to migrate from a WebSphere® Application Server, Network Deployment Version 6.1
or above deployment manager to a Version 8.5 deployment manager.
Before you begin
Supported configurations: This
article is about configuration migration, such as migrating deployment
managers and federated nodes in a network deployment environment.
The Application Migration Toolkit for WebSphere Application Server
provides support for migrating applications from previous versions
of WebSphere Application Server to the latest product version. For
information about migrating applications, read more about the Application
Migration Toolkit.
sptcfg
For resources to help you plan and
perform your migration, visit Knowledge Collection: Migration planning for WebSphere Application Server.
Mixed-version environment: Migrate the
WebSphere Application Server Version 6.1 or
above deployment manager to
Version 8.5 before migrating
the federated nodes that comprise the cell. The deployment manager
must always be at the highest release and fix level within a cell
for it to manage all nodes in the cell. The
Version 8.5 deployment manager
can manage Version 6.1 or above, and
Version 8.5 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.
mixv
Tip: Before
migrating a WebSphere Application Server Version 6.1 or above 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. See backupConfig command article
in the information center for more information. Make sure that you
note the exact name and location of this backed-up configuration.
For help in troubleshooting problems when migrating, read Troubleshooting migration.
Procedure
- Stop the Version 6.1 or above deployment manager.
Use the stopManager command from the app_server_root/bin directory.
For example:
![[AIX]](../images/aixlogo.gif)
![[HP-UX]](../images/hpux.gif)
![[Linux]](../images/linux.gif)
./stopManager.sh
stopManager.bat
See stopManager command for more information.
If you have security enabled, specify the -user and -password
parameters of the command.
You can migrate a Version 6.1 or
above deployment manager whether it is running or stopped. The migration
tools can retrieve all the configuration data either way. You must
stop the Version 6.1 or above deployment manager before you can start
the Version 8.5 deployment
manager that you are installing, however, so it makes sense to stop
it now.
- Use the migration tools to migrate the Version 6.1 or above
configuration to Version 8.5.
The Migration wizard, which
is the graphical interface to the Version 8.5 command-line migration
tools (WASPreUpgrade and WASPostUpgrade), is the recommended migration
tool.
- Install the Version 8.5 product on the same machine as the Version 6.1 or above deployment
manager.
See Installing and configuring your application
serving environment for more information.
- Determine the cell name of the Version 6.1 or above WebSphere Application Server, Network Deployment cell.
Note: For a deployment manager migration, the Version 8.5 cell name must match
the name in the Version 6.1 or above configuration.
- Optional: Create a new Version 8.5 deployment manager
profile with the same cell name as the Version 6.1 or above cell.
Restrictions for a deployment manager migration: - The Version 8.5 cell
name must match the cell name in the Version 6.1 or above configuration.
If you create a profile with a new cell name, the migration will
fail.
- Either one or the other of the following options must be true:
- The Version 8.5 deployment
manager node name must be the same as the Version 6.1 or above deployment
manager node name.
- The Version 8.5 deployment
manager node name must be different from every node name in the Version
6.1 or above configuration.
Otherwise, the migration fails with the following message:MIGR0488E: The deployment manager node name in
the new configuration ({0}) cannot be the same
as a nodeagent node in the old configuration.
See manageprofiles command for more information.
If you also use the same node name that you used for the Version
6.1 or above cell, the node agents will still work after migration
without being restarted.
- Stop the Version 8.5 deployment manager.
- Use the Migration wizard or the command line tools to
migrate the deployment manager to Version 8.5.
- Start the Version 8.5 deployment manager.
- Optional: Uninstall the Version 6.1 or above
deployment manager.
Perform this step only after you
are certain that you have successfully migrated the configuration
of the deployment manager that you intend to delete.
- See Migrating a Version 6.1, 7.x, or 8.0 federated
node for information on iteratively migrating each federated
node to Version 8.5.
Results
After the deployment manager is upgraded to Version 8.5, each node in the
cell can be upgraded incrementally, one at a time. See Migrating
a Version 6.1, 7.x, or 8.0 federated node for more information.