Use the migration tools to migrate from WebSphere Application Server Network Deployment Version 5.x or 6.0.x to Network Deployment Version 6.1.
See Overview of migration, coexistence, and interoperability and Premigration considerations.
See Checking for the product-configuration migration prerequisites to determine the currently installed product level of WebSphere Application Server.
For help in troubleshooting problems when migrating, see Troubleshooting migration.
Before following these instructions, perform the actions in Preparing for product-configuration migration.
After you migrate the Version 5.x or 6.0.x deployment manager to a Version 6.1 deployment manager, you are no longer able to use the Version 5.x or 6.0.x deployment manager. You are only able to use the Version 6.1 deployment manager.
The Version 5.x or 6.0.x nodes can run in a Version 6.1 deployment cell.
After you migrate the Version 5.x or 6.0.x node to a Version 6.1 node, you are no longer able to use the Version 5.x or 6.0.x node. You are only able to use the Version 6.1 node.
If necessary, you can now roll back the federated node that you just migrated. See Rolling back a managed node.
This step can be skipped if you are migrating to the Version 6.1 default profile.
STRQSH
app_server_root/bin/dspwasinst -instance 5.x_or_6.0.x_profile_namewhere
Make note of the Name service port setting in the Additional ports section. This setting will be used as the starting point when you create the new Version 6.1 deployment manager profile in the next step.
app_server_root/bin/manageprofiles -create -profileName 61ND_profile_name -startingPort starting_port_numberwhere
STRQSH
app_server_root/bin/WASPreUpgrade backup_directory_name old_profile_rootwhere
The directory is created if it does not already exist. Additionally, the tool writes a log file called WASPreUpgrade.log that chronicles the steps taken by the WASPreUpgrade command.
For a full explanation of the WASPreUpgrade command and its parameters, see WASPreUpgrade command.
STRQSH
app_server_root/bin/WASPostUpgrade backup_directory_name -profileName 61ND_profile_name -replacePorts truewhere
For a full explanation of the WASPostUpgrade command and its parameters, see WASPostUpgrade command.
STRQSH
STRSBS QWAS61/QWAS61
app_server_root/bin/startManager -profileName 61ND_profile_namewhere
app_server_root/bin/startNode -instance 5.x_or_6.0.x_profile_namewhere
app_server_root/bin/startServer -instance 5.x_or_6.0.x_profile_name 5.x_or_6.0.x_application_server_namewhere
Skip the instruction that tells you to start the Version 6.1 profile that receives the WebSphere Application Server Version 5.x or 6.0.x configuration.
Specify -replacePorts true when you run the WASPostUpgrade script. This allows the Version 6.1 federated node to use the same virtual host ports and transport ports as the Version 5.x or 6.0.x federated node.
STRQSH
app_server_root/bin/startNode -profileName 6.1_profile_namewhere
app_server_root/bin/startServer -profileName 6.1_profile_name 6.1_application_server_namewhere