The migration tools of WebSphere Application Server, Version 6 support migrating a V5.x configuration instance to a V6 profile.
Before you begin
This task describes how to migrate the configuration of a V5.x configuration instance to a V6 profile. This task describes how to use the V6 migration tools to perform the migration.Why and when to perform this task
If the node you are migrating is part of a deployment manager cell, migrate the V5.x deployment manager to V6 as described in the information center for Network Deployment first, before continuing this procedure. The deployment manager node must always be at the highest release level within the cell.Steps for this task
stopServer.sh server1 stopServer.sh server2
If security is enabled, specify the -user and -password parameters on the stopServer command.
You can migrate a V5.x node without stopping it. But it is not necessary to have the node running to migrate its configuration. The migration tools can retrieve all the configuration data while the node is stopped. You must stop the node before you can start the V6 node that you are installing.
./WASPreUpgrade.sh <backupDirectory> <V5_location>
WASPreUpgrade.bat <backupDirectory> <V5_location>
./WASPostUpgrade.sh <backupDirectory> -oldProfile <host_instanceName> -profileName <ProfileName>
WASPostUpgrade.bat <backupDirectory> -oldProfile <host_instanceName> -profileName <ProfileName>
Result
You have upgraded a Version 5.x configuration instance to a Version 6 profile.What to do next
Return to Migrating configuration data to continue.Related tasks
Migrating product configurations
Related reference
The WASPreUpgrade command
The WASPostUpgrade command
The clientUpgrade command
The convertScriptCompatibility command