Use the migration tools to migrate a WebSphere® Application Server, Network Deployment Version 6.x cell to a Version 8.0 WebSphere Application Server, Network Deployment cell.
This topic is about configuration migration, such as migrating deployment managers and federated nodes in a network deployment environment. The Application Migration Toolkit for WebSphere Application Server provides support for migrating applications from previous versions of WebSphere Application Server to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.
sptcfgRead Overview of migration, coexistence, and interoperability and Premigration considerations.
For resources to help you plan and perform your migration, visit Knowledge Collection: Migration planning for WebSphere Application Server.
Read Checking for the product-configuration migration prerequisites to determine the currently installed product level of WebSphere Application Server.
For help, read Troubleshooting migration.
Before following these instructions, perform the actions in Preparing for product-configuration migration.
After you migrate the Version 6.x deployment manager to a Version 8.0 deployment manager, you are no longer able to use the Version 6.x deployment manager. You are only able to use the Version 8.0 deployment manager.
The Version 6.x nodes can run in a Version 8.0 WebSphere Application Server, Network Deployment cell.
After you migrate the Version 6.x node to a Version 8.0 node, you are no longer able to use the Version 6.x node. You are only able to use the Version 8.0 node.
Read the "backupConfig command" article in the information center for more information.
Read the "backupConfig command" article in the information center for more information.
If necessary, you can now roll back the federated node that you just migrated. Read Rolling back a federated node for more information.
This step can be skipped if you are migrating to the Version 8.0 default profile.
STRQSH
app_server_root/bin/dspwasinst -instance 6.x_profile_namewhere
The name of the Version 6.x node is listed in the Node section, and the name of the cell is listed in the Cell section.
Also 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 8.0 deployment-manager management profile in the next step.
app_server_root/bin/manageprofiles -create -profileName 80ND_profile_name -startingPort starting_port_number -templatePath app_server_root/profileTemplates/dmgr -cellName 6x_cell_name -nodeName 6x_node_namewhere
This parameter must be identical to the Version 6.x instance or profile that is to be migrated.
The source and target cell names must be identical when migrating to Version 8.0.
The source and target node names must be identical when migrating to Version 8.0.
For details on the syntax and parameters of the manageprofiles command, read the "manageprofiles command" article in the information center.
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, read WASPreUpgrade command.
STRQSH
app_server_root/bin/WASPostUpgrade backup_directory_name -profileName 80ND_profile_name -replacePorts truewhere
For a full explanation of the WASPostUpgrade command and its parameters, read WASPostUpgrade command.
STRQSH
STRSBS QWAS8/QWAS8
app_server_root/bin/startManager -profileName 80ND_profile_namewhere
app_server_root/bin/startNode -instance 6.x_profile_namewhere
app_server_root/bin/startServer -instance 6.x_profile_name 6.x_application_server_namewhere
STRQSH
app_server_root/bin/dspwasinst -instance 6x_profile_namewhere
app_server_root/bin/manageprofiles -create -profileName 80_profile_name -startingPort starting_port_number -templatePath app_server_root/profileTemplates/default -serverName 6x_application_server_name -nodeName 6x_node_namewhere
This parameter must be identical to the Version 6.x instance or profile that is to be migrated.
The source and target node names must be identical when migrating to Version 8.0.
Skip the instruction that tells you to start the Version 8.0 profile that receives the WebSphere Application Server Version 6.x configuration.
Specify -replacePorts true when you run the WASPostUpgrade script. This allows the Version 8.0 federated node to use the same virtual host ports and transport ports as the Version 6.x federated node.
STRQSH
app_server_root/bin/WASPreUpgrade backup_directory_name profile_rootwhere
The directory is created if it does not already exist. It is also the directory where the WASPreUpgrade migration 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, read WASPreUpgrade command.
STRQSH
app_server_root/bin/WASPostUpgrade backup_directory_name -profileName 80_profile_name [-portBlock port_starting_number]where
It is recommended that you always specify the -portBlock parameter if you do not want your profile's ports to conflict with the default profile's ports.
For a full explanation of the WASPostUpgrade command and its parameters, read WASPostUpgrade command.
STRQSH
app_server_root/bin/startNode -profileName 8.0_profile_namewhere
app_server_root/bin/startServer -profileName 8.0_profile_name 8.0_application_server_namewhere