Version 6 migration always works by migrating an earlier supported version of WebSphere Application Server to a deployment manager profile.
Before you begin
Collect the following information about your V4 installation before you begin this procedure. The Migration wizard prompts you for the information during the migration.
Panel and field in wizard | Version 4 product | Record your value here | Link to description of field | ||
---|---|---|---|---|---|
V4.0.y AEs | V4.0.y AE | V4.1.y EE | |||
Installation root directory | Yes | Yes | Yes | See WASPreUpgrade command for a description of the currentWebSphereDirectory parameter. | |
Configuration file name | Optional: Defaults to config/server-cfg.xml file. | No | Required. | The name of the XML configuration file to process. See WASPreUpgrade command for a description of the import parameter. |
|
Use port values assigned to previous installation? | Optional; defaults to false. | Optional; defaults to false. | Optional; defaults to false. | 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. |
Before using the Migration wizard, you must have access to the existing, previous version of WebSphere Application Server. You must also have a valid Version 6 deployment manager profile to serve as the target of the migration.
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 Version 4.x Application Server to a Version 6 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.
Panel and field in wizard | Record your value here | Link to description of field |
---|---|---|
Backup directory name | See WASPreUpgrade command or WASPostUpgrade command for a description of the backupDirectoryName parameter. | |
Profile name | See WASPostUpgrade command for a description of the profileName parameter. |
After gathering all of the information that is required during the migration, use the wizard to migrate a V4.x Application Server 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. Version 4.0.y AEs requires you to identify the location of the configuration file. You do not need to identify the location of the configuration file for other V4 editions.
If the previous version specification is correct, the wizard displays the Migration backup directory panel.
If the V6 profile 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 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.