Use the migration tools to migrate a Version 5.x application server configuration instance to a Version 6.0.x application server profile.
Before you begin
If the node you are migrating is part of a deployment manager cell, migrate the Version 5.x deployment manager to Version 6.0.x 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 Version 5.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 Version 6.0.x node that you are installing.
./stopNode.sh
If security is enabled, specify the -user and -password parameters on the stopNode command.
From the Version 6.0.x node's profile_name/bin directory, run the following command:
./WASPreUpgrade.sh backupDirectory V5_location
WASPreUpgrade.bat backupDirectory V5_location
From the Version 6.0.x node's profile_name/bin directory, run the following command:
./WASPostUpgrade.sh backupDirectory -oldProfile host_instance_name -profileName profile_name
WASPostUpgrade.bat backupDirectory -oldProfile host_instance_name -profileName profile_name
Result
You have upgraded a Version 5.x configuration instance to a Version 6.0.x profile.What to do next
Return to Migrating product configurations to continue.Related concepts
Migration tools
Related tasks
Migrating product configurations
Migrating from Version 5.x to a Version 6.0.x stand-alone application
server on a remote machine
Related reference
WASPreUpgrade command
WASPostUpgrade command
The clientUpgrade command
convertScriptCompatibility command