Migrating Network Deployment, V5.0.0 or V5.0.1 with embedded messaging to V5.1

The migration tools of WebSphere Application Server Network Deployment, V5.1 support migrating Network Deployment, V5.0.0 or Version 5.0.1 with embedded messaging to V5.1.

 

Overview

This topic describes migrating WebSphere Application Server Network Deployment, V5.0.0 or V5.0.1 with the embedded messaging client feature installed, to V5.1. If you are migrating a V5.0.0 or V5.0.1 deployment manager without the embedded messaging client, or if you are migrating a V5.0.2 deployment manager, see Migrating Network Deployment, V5.0.x to V5.1.

 

Overview

The embedded messaging feature places certain restrictions on migrating V5.0.0 or V5.0.1 nodes to V5.1. If embedded messaging is not involved, you can migrate any level of V5.0.x to a V5.1 during the installation of the V5.1 Network Deployment product. If the embedded messaging client is installed on the V5.0.0 or V5.0.1 deployment manager node, first either upgrade the node to V5.0.2, or use this task to perform the manual migration procedure for V5.0.0 or V5.0.1 deployment manager nodes with the embedded messaging client.

1. Stop the V5.0.0 or V5.0.1 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.

   You can migrate a V5.0.0 or V5.0.1 node without stopping it. But it is not necessary to have the node running to migrate its configuration. The migration tools can retrieve all the configuration data while the node is stopped. And you must stop the node before you can start the V5.1 node that you are installing. So, you can stop the node now.

   
   Migration tip

   ---

   Operating platform	Tip in Platform-specific tips for installing and migrating
   All platforms	Avoiding the use of a V5.0.x deployment manager after migrating to V5.1

   
   
   

   ---

2. Obtain the V5.1 product CD-ROM.On this CD is the migration/bin directory. This directory contains a special environment that you can use to run the WASPreUpgrade tool without installing V5.1.

3. Save the current configuration using the WASPreUpgrade command script from the /migration/bin directory of the V5.1 product CD-ROM.Save the configuration in the migration-specific-backup directory on the V5.0.0 or V5.0.1 machine.

   WASPreUpgrade /opt/tmp/migration-specific-backup /opt/websphere/deploymentmanager

   The WASPreUpgrade tool provides status to the screen and to log files in the /migration-specific-backup directory. ASCII log file names start with the text "WASPreUpgrade" and include a date timestamp.

4. Uninstall the V5.0.0 or V5.0.1 deployment manager node.Use the following steps to uninstall the node:

   1. Run the uninstall command from the install_root\_uninst directory of the product that you are uninstalling.

   2. Run the platform-specific uninstalling procedure to complete the removal by removing all artifacts of the earlier product from the system, as described in Uninstalling manually.

5. Install V5.1 of Network Deployment without selecting the migration option if it appears, as described in Installing the product.

6. Add the V5.0.0 or V5.0.1 configuration to the V5.1 configuration. Use the WASPostUpgrade command tool in the install_root/bin directory of the V5.1 installation root directory to add the V5.0.0 or V5.0.1 configuration to the V5.1 configuration.

   WASPostUpgrade /opt/tmp/migration-specific-backup

 

Results

You can use the migration tools to migrate V5.0.0 or V5.0.1 of Network Deployment with the embedded messaging client to V5.1.

 

What to do next

Return to Migrating Network Deployment, V5.0.x to V5.1 to continue migrating the cell.

---

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

 

---