Version 6 migration always works by migrating an earlier supported version of WebSphere Application Server to a deployment manager profile.
Before you begin
See WASPreUpgrade command for a description of the currentWebSphereDirectory parameter.
Specifying “true” causes any ports of matching VirtualHosts to first be removed from the new configuration before adding the new values.
Specifying “false” for this parameter will just add new port values.
See WASPostUpgrade command for a description of the replacePorts parameter.
See WASPreUpgrade command for a description of the backupDirectory parameter.
See WASPostUpgrade command for a description of the profileName parameter.
Before using the Migration wizard, you must have access to the existing V5 deployment manager. You must also have a valid Version 6 deployment manager profile to serve as the target of the migration.
You should have installed Version 6 already. Use the Profile creation wizard to create a new target profile if the deployment manager target for the migration does not yet exist. After verifying that a valid Version 6 target exists, you can start the procedure.
The Network Deployment product does not create a deployment manager profile during installation because there are three profile types that you might require on any machine.
The Installation wizard prompts you to use the Profile creation wizard at the end of installing the core product files. However, using the Profile creation wizard at that time is optional.
Create a deployment manager profile if you have not already created one.
Why and when to perform this task
This topic describes using the Migration wizard to migrate a V5.x deployment manager to a V6 deployment manager.
The Migration wizard is new as of Version 6. The wizard is the graphical interface to the Version 6 migration tools, which are the WASPreUpgrade command and the WASPostUpgrade command. The migration tools are command-line tools.
After gathering all of the information that is required during the migration, use the wizard to migrate a V5 deployment manager to the V6 deployment manager.
Steps for this task
The First steps console starts the Migration wizard. The wizard displays its Welcome panel.
The wizard displays the Detected versions of WebSphere Application Server panel.
Select the check box to specify the location of a previous installation that might not appear in the list.
If the V5 previous version is valid, the wizard displays the Target profile selection panel.
Use the Profile creation wizard to create a target deployment manager profile for the migration if one does not yet exist.
Installing the Network Deployment product does not automatically create a profile.
The V6 deployment manager must be running whenever you migrate a V5 deployment manager to it.
The V6 deployment manager must have the same cell name as the V5 cell.
After migrating a V5 deployment manager, you can migrate a V5 managed node to a V6 managed node. If you are migrating a V5.x managed node to a V6 managed node, the node names must match. When you create the profile, use the node name of the V5 managed node that you intend to migrate. See Migrating a V5.x managed node to a V6 managed node for more information.
If the cell name does not match, the wizard displays a warning panel.
The wizard displays the Port value assignment panel.
The wizard displays the Deployment manager verification panel that warns you to verify that the deployment manager is running.
The wizard begins the premigration. The wizard displays a Migration status panel during the premigration.
If the premigration is not successful, the wizard displays a failure panel. If the premigration is partially successful, the wizard displays a warning panel.
Correct any problems and retry the migration.
If the premigration is successful, the wizard displays an indication of success.
If the postmigration is not successful, the wizard displays a failure panel. If the postmigration is partially successful, the wizard displays a warning panel.
Correct any problems and retry the migration.
If the postmigration is successful, the wizard displays an indication of success.
What to do next
Refer to Using the Profile creation wizard to learn more about the creating profiles.
Refer to the description of the wasprofile command to learn more about the command-line tool, and to see examples of how to use the command.
See Migrating a V5.x managed node to a V6 managed node to get started migrating individual managed node to V6.Related tasks
Migrating a V5.x managed node to a V6 managed node