Migrating from Network Deployment Version 5.x to a Version 6.0.x deployment manager

Use the migration tools to migrate from Network Deployment Version 5.x to a Version 6.0.x deployment manager.

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 Version 6.0.x, 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.

Restriction: Migrating to a Version 6.0.x deployment manager on a remote machine is not supported.


Use the following procedure to migrate the deployment manager.

Procedure 

1.  Stop the Version 5.x deployment manager.

Use the stopManager command from the app_server_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.

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.

2. Use the migration tools to migrate the Version 5.x configuration
to Version 6.0.x. The Migration wizard, which is the graphical interface to the
Version 6.0.x command-line migration tools (WASPreUpgrade command and WASPostUpgrade command), 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 Version 6.0.x product on the same machine as the Version 5.x deployment manager.
2. Create a new deployment manager profile with the same cell name as the Version 5.x cell. You should also use the same node name as the Version 5.x cell. This makes migration smoother, because the Version 5.x node agents will still work without being restarted.
3. Verify the installation of the Version 6.0.x deployment manager. Use the First Steps tool when it opens 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 Version 6.0.x deployment manager.
5. Use the Migration wizard to migrate the deployment manager to Version 6.0.x.
6. Start the Version 6.0.x deployment manager.
7. Optional: Uninstall the Version 5.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 Version 5.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 Version 5.x Network Deployment environment can be enabled by running the following JACL script from the Version 5.x Network Deployment/bin directory:

   migrationDisablementReversal.jacl

8. See Migrating a Version 5.x managed node to a Version 6.0.x managed node for information on iteratively migrating each federated node to Version 6.0.x.   

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_migratend50x.html