Use the migration tools to migrate a WebSphere® Application Server, Network Deployment Version 6.1
cell to a Version 8.5 WebSphere Application Server, Network Deployment cell.
Before you begin
Supported configurations: This
article 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.
sptcfg
Read 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.
Migration of a
WebSphere Application Server, Network Deployment Version 6.1
deployment manager and associated federated nodes can be performed
in stages.
- Migrate the WebSphere Application Server Version 6.1 deployment manager to a Version 8.5 deployment manager.
After you migrate the Version 6.1 deployment manager to a Version 8.5 deployment manager,
you are no longer able to use the Version 6.1 deployment manager.
You are only able to use the Version 8.5 deployment manager.
The Version 6.1 nodes can run in a Version 8.5 WebSphere Application Server, Network Deployment cell.
Tip: Before migrating a WebSphere Application Server Version 6.1 deployment
manager, use the backupConfig command or your own
preferred backup utility to back up your existing configuration if
you want to be able to restore it to its previous state after migration.
See backupConfig command for more information. Make sure
that you note the exact name and location of this backed-up configuration.
- Migrate each WebSphere Application Server Version 6.1 node to Version 8.5.
After you migrate the Version 6.1 node to a Version 8.5 node, you are no
longer able to use the Version 6.1 node. You are only able to use
the Version 8.5 node.
Tip: When migrating a
WebSphere Application Server Version 6.1 federated
node, you must perform the following actions if you want to be able
to roll it back to its previous state after migration:
- Back up your existing configuration using the backupConfig command or your own preferred backup utility.
- Run the backupConfig command or your own preferred
utility to back up the Version 8.5 deployment manager configuration.
- Run the backupConfig command or your own preferred
utility to back up the Version 6.1 federated node configuration.
Important: Make sure that you note the exact name
and location of this backed-up configuration.
See backupConfig
command for more information.
- Migrate the federated node.
If necessary, you can now roll back the federated node that
you just migrated. Read Rolling back a federated node for
more information.
Procedure
- Create a WebSphere Application Server Version 8.5 deployment-manager
management profile to receive the Version 6.1 deployment manager configuration.
This step can be skipped if you are migrating to the Version 8.5 default profile.
- Start the Qshell environment so that you can run WebSphere Application Server scripts.
Enter the following command from a command line:
STRQSH
- Run the dspwasinst script to display
information about the Version 6.1 deployment manager profile.
Use the following parameters:
app_server_root/bin/dspwasinst
-instance 6.1_profile_name
where
- app_server_root is the location
of the Version 6.1 installation that contains the deployment manager
to be migrated
- 6.1_profile_name is the name
of the Version 6.1 deployment manager profile that is to be migrated
The name of the Version 6.1 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.5 deployment-manager
management profile in the next step.
- Run the manageprofiles command.
Use the following parameters:
app_server_root/bin/manageprofiles
-create
-profileName 85ND_profile_name
-startingPort starting_port_number
-templatePath app_server_root/profileTemplates/dmgr
-cellName 61_cell_name
-nodeName 61_node_name
where
- app_server_root is the location
where Version 8.5 is installed
- 85ND_profile_name is the name
of your Version 8.5 deployment-manager
management profile
This parameter must be identical to the Version
6.1 instance or profile that is to be migrated.
- starting_port_number is the
first of a block of 10 consecutive ports
- 61_cell_name is the name of
the Version 6.1 cell obtained in the previous step
The source and
target cell names must be identical when migrating to Version 8.5.
- 61_node_name is the Version
6.1 node name obtained in the previous step
The source and target
node names must be identical when migrating to Version 8.5.
For details on the syntax and parameters of the manageprofiles command, read the "manageprofiles command"
article in the information center.
- Save the WebSphere Application Server Version 6.1 deployment manager configuration.
- Start the Qshell environment so that you can run WebSphere Application Server scripts.
Enter the following command from a command line:
STRQSH
- Run the WASPreUpgrade script.
Use the following parameters:
app_server_root/bin/WASPreUpgrade
backup_directory_name
old_profile_root
where
For a full explanation of the WASPreUpgrade command and its parameters, read WASPreUpgrade command.
- Restore the WebSphere Application Server Version 6.1 deployment manager configuration into the Version 8.5 deployment-manager
management profile.
- Start the Qshell environment so that you can run WebSphere Application Server scripts.
Enter the following command from a command line:
STRQSH
- Run the WASPostUpgrade script.
Use the following parameters:
app_server_root/bin/WASPostUpgrade
backup_directory_name
-profileName 85ND_profile_name
-replacePorts true
where
- app_server_root is the location
where Version 8.5 is installed
- backup_directory_name (required
parameter) is the fully qualified path to the integrated file system
directory that the WASPreUpgrade migration tool
previously used to save the Version 6.1 deployment manager configuration
- 85ND_profile_name (required
parameter) is the name of the Version 8.5 deployment-manager
management profile to which the script migrates your configuration
- -replacePorts true replaces all virtual host
alias port and transport settings in the Version 8.5 profile with the
settings from the Version 6.1 instance or profile during migration
For a full explanation of the WASPostUpgrade command and its parameters, read WASPostUpgrade command.
- Start the WebSphere Application Server Version 8.5 deployment-manager
management profile.
- Start the Qshell environment so that you can run WebSphere Application Server scripts.
Enter the following command from a command line:
STRQSH
- Verify that the Version 6.1 deployment manager, node
agent, and federated nodes are stopped for the Version 6.1 deployment
manager that was migrated.
- If the QWAS85 subsystem has not been started, start
the default profile.
Enter the following command from
a command line:
STRSBS QWAS85/QWAS85
- Start the Version 8.5 deployment manager using the startManager script.
Use the following parameters:
app_server_root/bin/startManager
-profileName 85ND_profile_name
where
- app_server_root is the location
where Version 8.5 is installed
- 85ND_profile_name is the name
of the Version 8.5 deployment-manager
management profile
- Start the Version 6.1 node agent and federated nodes.
- Start the Version 6.1 node agent using the startNode script.
Use the following parameters:
app_server_root/bin/startNode
-instance 6.1_profile_name
where
- app_server_root is the location
of the Version 6.1 installation that contains the federated node
- 6.1_profile_name is the name
of the Version 6.1 instance or profile for the federated node
- Start the Version 6.1 federated node using the startServer script.
Use the following parameters:
app_server_root/bin/startServer
-instance 6.1_profile_name
6.1_application_server_name
where
- app_server_root is the location
of the Version 6.1 installation that contains the federated node
- 6.1_profile_name is the name
of the Version 6.1 instance or profile for the federated node
- 6.1_application_server_name is the name of the Version 6.1 application server
- Migrate the WebSphere Application Server Version 6.1 federated nodes to Version 8.5.
- Verify that the Version 6.1 node agent and federated
node are stopped for the federated profile that is to be migrated
to Version 8.5.
- Verify that the Version 8.5 deployment manager
is running.
- Complete the following instructions for each Version
6.1 federated node that is to be migrated to Version 8.5.
- Create a WebSphere Application Server Version 8.5 profile to
receive the Version 6.1 configuration.
- Start the Qshell environment so that you can run WebSphere Application Server scripts.
Enter
the following command from a command line:
STRQSH
- Run the dspwasinst script to obtain the node name and server name for the Version 6.1
instance or profile that is to be migrated.
Use the following parameters:
app_server_root/bin/dspwasinst
-instance 61_profile_name
where
- app_server_root is the location
of the Version 6.1 installation that contains the instance or profile
to be migrated
- 61_profile_name is the name
of the Version 6.1 instance or profile that is to be migrated
The name of the Version 6.1 node is listed in the
Node section, and the name of the server is listed in the
Information
for server section.
- Run the manageprofiles script.
Use the following parameters:
app_server_root/bin/manageprofiles
-create
-profileName 85_profile_name
-startingPort starting_port_number
-templatePath app_server_root/profileTemplates/default
-serverName 61_application_server_name
-nodeName 61_node_name
where
For details on the syntax and parameters of the manageprofiles
command, read the "manageprofiles command" article in the information
center.
Tip: If you make any cell-level changes to the new
Version 8.5 node before migration,
such as changes to virtual-host information, these changes will be
lost during migration. Therefore, you should wait until after the
node has been migrated before making any such changes. Otherwise,
you will have to manually remake all of the changes, such as any changes
to the virtual-host and host-alias information, to the new cell after
migration using the administrative console running on the deployment
manager. This tip is reflected in message MIGR0444W.
Skip the instruction
that tells you to start the Version 8.5 profile that receives
the WebSphere Application Server Version
6.1 configuration.
Specify -replacePorts true when you run the WASPostUpgrade script. This
allows the Version 8.5 federated
node to use the same virtual host ports and transport ports as the
Version 6.1 federated node.
- Save the WebSphere Application Server Version 6.1 configuration.
- Start the Qshell environment so that you can run WebSphere Application Server scripts.
Enter
the following command from a command line:
STRQSH
- Run the WASPreUpgrade script.
Use the following
parameters:
app_server_root/bin/WASPreUpgrade
backup_directory_name
profile_root
where
For a full explanation of the WASPreUpgrade command and its parameters, read WASPreUpgrade command.
- Restore the WebSphere Application Server Version 6.1 configuration into a Version 8.5 profile.
- Start the Qshell environment so that you can run WebSphere Application Server scripts.
Enter
the following command from a command line:
STRQSH
- Run the WASPostUpgrade script.
Use the following
parameters:
app_server_root/bin/WASPostUpgrade
backup_directory_name
-profileName 85_profile_name
[-portBlock port_starting_number]
where
For a full explanation of the WASPostUpgrade command and its parameters, read WASPostUpgrade command.
- Start the WebSphere Application Server Version 8.5 node agent
and federated nodes.
- Start the Qshell environment so that you can run WebSphere Application Server scripts.
Enter
the following command from a command line:
STRQSH
- Start the Version 8.5 node agent using the startNode script.
Use
the following parameters:
app_server_root/bin/startNode
-profileName 8.5_profile_name
where
- app_server_root is the location
where Version 8.5 is installed
- 8.5_profile_name is the name
of the Version 8.5 profile
for the federated node
- Start the Version 8.5 federated node using the startServer script.
Use the following parameters:
app_server_root/bin/startServer
-profileName 8.5_profile_name
8.5_application_server_name
where
- app_server_root is the location
where Version 8.5 is installed
- 8.5_profile_name is the name
of the Version 8.5 profile
for the federated node
- 8.5_application_server_name is the name of the Version 8.5 application server