The migration tools of WebSphere Application Server Network Deployment Version 6 support migrating a configuration instance of Network Deployment Version 5.x to a Network Deployment Version 6 profile.
Before you begin
This topic describes migrating a V5.x Network Deployment configuration instance to a V6 profile.Migrate V5.x of WebSphere Application Server Network Deployment to V6 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 V6, the deployment manager has the capability to manage both V6 and V5.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 application server that is part of a network deployment cell, and you want to migrate the cell from a Version 5 to a Version 6 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 V5.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 V5.x deployment manager before you can start the V6 deployment manager that you are installing, so it makes sense to stop it now.
./WASPreUpgrade.sh <backupDmgrDir> <V5_location>
WASPreUpgrade.bat <backupDmgrDir> <V5_location>
./WASPostUpgrade.sh <backupDmgrDir> -oldProfile <host_instanceName> -profileName <dmgrProfileName>
WASPostUpgrade.bat <backupDmgrDir> -oldProfile <host_instanceName> -profileName <dmgrProfileName>
migrationDisablementReversal.jacl
Result
After the deployment manager is upgraded to V6, each node in the cell may then be upgraded incrementally, one at a time. The following diagram illustrates a mixed-release cell containing a V6 deployment manager with both V5 and V6 managed nodes:
The migration tools migrate V5.x Samples to the V6 Network Deployment node, to support cell members at the V5.x level. If the migration did not migrate the V5.x Samples, a synchronization would remove the Samples from the V5.x nodes. After migrating all federated nodes to V6, the V5.x Samples remain in the configuration. You can remove the V5.x Samples at that time or replace them with the V6 samples.
What to do next
Return to Migrating configuration data to continue.Related concepts
Migration tools
Related reference
addNode command
removeNode command
serverStatus command
startNode command
startServer command
stopNode command
stopServer command
startManager command
stopManager command