pre_uninst50ws command

 

The pre_uninst50ws command is a V5.1 migration tool for use when you migrate a federated V5.0.x node to V5.1. The pre_uninst50ws command changes the normal uninstaller program environment to prevent the uninstaller program from removing the V5.0.x or V5.1 node from the deployment manager cell while uninstalling the base V5.0.x or V5.1 node. The script also prevents the uninstaller program from removing the jmsserver process, which is the embedded messaging queue manager for the federated node.

A problem can occur when you uninstall an earlier version of the base WAS product that you migrated to Version 5.1. If the earlier node is federated, migrating the federated node to Version 5.1 gives you a federated V5.1 node, too. The new node has the same node name as the earlier node, and is a member of the same cell. The problem is that the uninstaller program issues a removeNode command when it uninstalls a federated node. So, if you uninstall the earlier version, the uninstaller issues a call to the deployment manager that requests the removal of the node from the cell. You are left with a V5.1 node that is configured as if it were a member of the cell and a deployment manager that does not recognize the node.

The pre_uninst50ws script overcomes the problem by renaming the _nodeuninst.sh or the _nodeuninst.bat script and creating a dummy script that prevents the uninstaller program from logging an error and stopping. Because the uninstaller program is not calling the script that removes the node from the cell, uninstalling the earlier version does not also unfederate the node from the cell. This lets you uninstall the previous node and still have a federated V5.1 node.

The post_uninst50ws migration tool restores the environment to allow the uninstaller program to remove a federated node from its cell while uninstalling the base node. If you are completely uninstalling the previous version, it is not necessary to run the post_uninst50ws script. If you follow the platform-specific instructions for uninstalling the previous version, you remove the _nodeuninst.sh or the _nodeuninst.bat script. So there is nothing left for the script to rename.

 

Location of the command file

The command file is located in the $WAS_HOME/bin directory of the V5.1 node.

If the installation wizard performs the initial migration, the wizard copies the scripts to the $WAS_HOME/bin directory of the V5.0.x node that it is migrating. If you migrate the node by calling the migration tool commands, you might have to copy the following files to the $WAS_HOME/bin directory of the V5.0.x node from the $WAS_HOME/bin directory of the V5.1 node...

• pre_uninst50ws.sh and post_uninst50ws.sh on a Linux or UNIX-based platform

• pre_uninst50ws.bat and post_uninst50ws.bat on a Windows platform

 

Recovering when you do not use the pre_uninst50ws script

If you uninstall a federated base node without running the pre_uninst50ws.sh script, you can recover by recreating whatever configuration data is lost. Lost configuration data includes any configuration that occurred while the original node was federated. Use the addNode.sh or the addNode.bat script in the bin directory of the installation root of the base Application Server node to add the new node back to the deployment manager cell. Do not use the -includeapps parameter to include applications from the node. The installer program included the applications into the deployment manager cell during installation. The removeNode.sh script does not delete applications from the cell.

 

Using the command when removing a V5.0.x node

The script is new as of Version 5.1.

1. Copy the script files described previously if the pre_uninst50ws command file is not in the $WAS_HOME/bin directory of the WebSphere Application Server, V5.x instance.

2. Run the pre_uninst50ws command from the $WAS_HOME/bin directory of the WAS, V5.x instance.

3. Uninstall the WAS, V5.x instance.

Run the post_uninst50ws script from a node only when you have run the pre_uninst50ws script on the node and decide not to uninstall the node.

 

Using the command when removing a V5.1 node

Use the pre_uninst50ws script if you uninstall V5.1 before uninstalling V5.0.2, to make V5.0.2 operational again.

For example, suppose you install V5.1 in spite of missing patches on your operating system and there are problems that require you to uninstall V5.1 to reinstall it. In the meantime, you bring up your V5.0.2 node to have a running WAS node. So you start up the V5.0.2 deployment manager, and the V5.0.2 node before uninstalling V5.1.

Uninstalling V5.1 removes the node from the deployment manager cell if and only if the V5.1 deployment manager is running. If the V5.0.2 deployment manager is running, the remove-node part of the uninstalling procedure fails because a V5.1 node cannot communicate with a V5.0.2 deployment manager. The V5.1 jmsserver process is not removed either.

However, if you start a V5.1 deployment manager, start the V5.0.2 node, and then uninstall the V5.1 node without running the pre_uninst50ws script, there are problems. Removing the V5.1 node causes the same effect as removing the V5.0.2 node. The deployment manager removes the configuration of the node. Follow this procedure to remove the V5.1 node without a problem.

1. Run the pre_uninst50ws script from the $WAS_HOME/bin directory of the WAS, Version 5.1 instance.

2. Run the pre_uninst502mq script from the $WAS_HOME/bin directory of the WAS, V5.2 instance if the embedded messaging feature is installed.

3. Uninstall the WAS, Version 5.1 instance.

Run the post_uninst50ws script from a node only when you have run the pre_uninst50ws script on the node and decide not to uninstall the node.

 

pre_uninst50ws.sh command syntax for Linux and UNIX-based platforms

The command syntax is as follows

pre_uninst50ws.sh

 

pre_uninst50ws.bat command syntax for Windows platforms

pre_uninst50ws.bat