Migrate Network Deployment, V5.x to a V6 deployment manager

The migration tools of WAS Network Deployment, V6 support migrating the configuration of Network Deployment, Version 5.x to Network Deployment, V6.

 

Before you begin

This topic describes migrating a V5.x deployment manager to V6.

Migrate V5.x of WAS Network Deployment to V6 before migrating the base nodes that comprise the cell. The deployment manager must always be at the highest release and fix level within a cell, to allow it to manage all nodes in the cell. In V6, the deployment manager has the capability to manage both V6 and V5.x release nodes (see Incremental cell upgrade for more information). 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 are migrating to a deployment manager on a remote machine, one can follow the steps outlined for an Application Server in Migrating V5.x of WAS to a V6 stand-alone Application Server on a remote machine. The steps are identical for a deployment manager.

 

Overview

Use the following procedure to migrate the deployment manager.

 

Procedure

1. Stop the V5.x deployment manager. Use the stopManager command from the install_root/bin directory. For example, use the following command on a Linux platform

   stopManager.sh 
   

   If you have security enabled, specify the -user and -password parameters of the command.

   We 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, stop the V5.x deployment manager before one can start the V6 deployment manager that you are installing, so it makes sense to stop it now.

2. Use the migration tools to migrate the V5.x configuration to V6. The Migration wizard, which is the graphical interface to the V6 command line migration tools (WASPreUpgrade and WASPostUpgrade), is the recommended migration tool. For detailed instructions and information on the new Migration wizard, see Using the Migration wizard. The instructions below describe migration using the command line migration tools.

   1. Install the V6 product on the same machine as the V5.x deployment manager.

   2. Create a new deployment manager profile with the same cell name as the V5.x cell. You should also use the same node name as the V5.x cell. This makes migration smoother, because the V5.x nodeagents will still work without being restarted.

   3. Verify the installation of the V6 deployment manager. Use the First Steps tool when it appears at the end of installing the product, or run the installation verification test yourself, if the First Steps tool does not appear for some reason.

   4. Stop the V6 deployment manager.

   5. Use the Migration wizard to migrate the deployment manager to V6.

   6. Start the V6 deployment manager.

   7. Optional: Uninstall the V5.x deployment manager. Perform this step only after you are certain that you have successfully migrated the configuration of the deployment manager you intend to delete. During migration processing, the V5.x Network Deployment environment will be disabled. This is done to prevent an unsupported scenario, such as a node being managed by two different cells, from occurring. The V5.x Network Deployment environment can be enabled by executing the following Jacl script from the V5.x Network Deployment/bin directory

      migrationDisablementReversal.jacl
      

   8. See Migrating a V5.x managed node to a V6 managed node for information on iteratively migrating each federated node to V6.

 

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. We 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.

---

 

See Also

Migration tools

 

See Also

addNode command
removeNode command
serverStatus command
startNode command
startServer command
stopNode command
stopServer command
startManager command
stopManager command

 

---