Use the migration tools to migrate a Version 5.x deployment manager configuration instance to a Version 6.0.x deployment manager profile.
Before you begin
Migrate WebSphere Application Server Network Deployment Version 5.x to Version 6.0.x before migrating the base nodes that comprise the cell. The Network Deployment node must always be at the highest release and fix level within a cell, to allow it to manage all nodes in the cell. Starting with Version 6.0, the deployment manager has the capability to manage both Version 6.0.x and Version 5.x release nodes. This allows a cell to be upgraded to a new release one node at a time, with minimal impact to the applications that are running within the cell.
If you have a Web services gateway running on a Version 5.x application server that is part of a Network Deployment cell, and you want to migrate the cell from a Version 5.x to a Version 6.0.x deployment manager, you must first preserve the gateway configuration as described in Co-existing with previous gateway versions.
Why and when to perform this task
Use the following procedure to migrate the deployment manager instance.
Steps for this task
./stopManager.sh
If you have security enabled, specify the -user and -password parameters of the command.
You can migrate a Version 5.x deployment manager without stopping it, but it is not necessary for it to be running for you to migrate its configuration. The migration tools can retrieve all the configuration data while the deployment manager is either running or stopped. However, you must stop the Version 5.x deployment manager before you can start the Version 6.0.x deployment manager that you are installing, so it makes sense to stop it now.
From the Version 6.0.x deployment manager's profile_name/bin directory, run the following command:
./WASPreUpgrade.sh backupDmgrDir V5_location
WASPreUpgrade.bat backupDmgrDir V5_location
From the Version 6.0.x deployment manager's profile_name/bin directory, run the following command:
./WASPostUpgrade.sh backupDmgrDir -oldProfile host_instance_name -profileName dmgr_profile_name
WASPostUpgrade.bat backupDmgrDir -oldProfile host_instance_name -profileName dmgr_profile_name
migrationDisablementReversal.jacl
Result
After the deployment manager is upgraded to Version 6.0.x, each node in the cell can then be upgraded incrementally, one at a time. The following diagram illustrates a mixed-release cell containing a Version 6.0.x deployment manager with both Version 5.x and Version 6.0.x managed nodes:
The migration tools migrate Version 5.x samples to the Version 6.0.x Network Deployment node, to support cell members at the Version 5.x level. If the migration did not migrate the Version 5.x samples, a synchronization would remove the samples from the Version 5.x nodes. After migrating all federated nodes to Version 6.0.x, the Version 5.x samples remain in the configuration. You can remove the Version 5.x samples at that time or replace them with the Version 6.0.x samples.
What to do next
Return to Migrating configuration data to continue.Related concepts
Migration tools
Related tasks
Migrating product configurations
Related reference
addNode command
removeNode command
serverStatus command
startNode command
startServer command
stopNode command
stopServer command
startManager command
stopManager command