[V5.1 and later]Uninstalling a base node that has the embedded messaging server and client feature

This task describes uninstalling a base WebSphere Application Server node after migrating from V5.0.2 to WebSphere Application Server, Version 5.1. In most situations you uninstall V5.0.2 after migrating to V5.1. However, some situations might require that you uninstall V5.1 while both versions are on the machine.

 

Overview

Before uninstalling, verify that you have no open Web browsers that are accessing the administrative console.

  1. Stop any browsers, delete any configuration instances, and stop any Java processes related to WebSphere Application Server products as described in Uninstalling the product.

  2. Identify which base node you are uninstalling.Uninstall either the V5.0.2 node and leave the V5.1 node installed, or uninstall the V5.1 node and leave the V5.0.2 node installed. Write down the installation root directory of the node you intend to uninstall if the path names are similar. Examples in this task use the following path names for nodes on a Linux platform:

    • V5.0.2: /opt/WebSphere/AppServer50

    • V5.1: /opt/WebSphere/AppServer51
    The required steps to uninstall each node are different. Each set of steps is presented as sub-steps in an optional step in this procedure.

  3. Change directories to the bin directory on the node you are uninstalling.Change directories to the install_root/bin directory on a Linux or UNIX-based platform, or to the install_root\bin directory on a Windows system.

    For example, issue this command to change directories on a Linux platform: 

    cd /opt/WebSphere/AppServer50/bin

  4. Run the pre_uninst50ws command to prevent removing the migrated-from node and the migrated-to node from the deployment manager cell and to preserve the jmsserver process, which is the embedded messaging queue manager for the federated base node.

    For example, run the following command on a Linux platform: 

    pre_uninst50ws.sh

    If you are uninstalling V5.0.2 and the script is not present in the V5.0.2 directory, copy it from the V5.1 directory.

    If you do not run this script, verify that the deployment manager is not running before uninstalling the product.

  5. (Optional)   Uninstall the V5.0.2 node.

    1. Change directories to the V5.1 install_root51/bin directory.

      For example, issue this command to change directories on a Linux platform: 

      cd /opt/WebSphere/AppServer51/bin

    2. Run the pre_uninst502mq command. The command helps avoid removing the embedded messaging feature code. On Windows platforms, the command creates dummy registry entries. On all platforms, the command creates a dummy queue manager, WAS_COEXIST, that helps retain the embedded messaging feature code. Run the script from the install_root/bin directory of the V5.1 installation: 

      pre_uninst502mq.sh

    3. Change directories to the install_root50/_uninst directory in the V5.0.2 installation root before issuing the uninstall command.The command file is located in the install_root50/_uninst directory on a Linux or UNIX-based platform, and in the install_root50\_uninst directory on a Windows system.

      For example, use this command to change directories on a Linux platform: 

      cd /opt/WebSphere/AppServer50/_uninst

    4. Issue the uninstall command.The command file is named uninstall for Linux and UNIX-based platforms and Uninstall.exe on Windows platforms. The command file for V5.0.x on Linux for S/390 platforms* is named uninstall.sh.

      *Linux for S/390 platforms refers to the Linux distributions available from Linux distributors that run on IBM eServer zSeries and S/390 systems in 31-bit mode.

      On Windows platforms, call the Uninstall.exe command: 

      install_root\_uninst\Uninstall.exe
      Call the program directly from the install_root\_uninst directory. For example, if the installation root is C:\WebSphere\AppServer50, issue the following command: 

      C:\WebSphere\AppServer50\_uninst> Uninstall.exe

      On Linux and UNIX-based platforms, issue the uninstall command from the install_root/_uninst directory: 

      uninstall
      (To uninstall V5.0.x on a Linux for S/390 platform, use the uninstall.sh script.)

    5. Change directories to the V5.1 install_root51/bin directory.

      For example, issue this command to change directories on a Linux platform: 

      cd /opt/WebSphere/AppServer51/bin

    6. Run the post_uninst502mq command. The command removes the dummy registry entries. Run the script from the install_root/bin directory of the V5.1 installation: 

      post_uninst502mq.sh

    7. Delete the dummy queue manager if it still exists.Issue the following commands from the install_root51/bin directory to delete the dummy queue manager: 

      endmqm WAS_COEXIST
dltmqm WAS_COEXIST

    8. Stop and restart the V5.1 Application Server.For example, run these commands from the install_root51/bin directory to recycle the server1 process on a Linux platform: 

      stopServer.sh server1

startNode.sh 

startServer.sh server1

    9. (Optional)   Uninstall manually before reinstalling.This step is required before you can reinstall the V5.0.x product into the same installation root directory. Otherwise reinstall the product into another directory.

  6. (Optional)   Uninstall the V5.1 node.

    1. Change directories to the V5.0.2 install_root50/bin directory. For example, issue this command to change directories on a Linux platform: 

      cd /opt/WebSphere/AppServer50/bin

    2. Change directories to the install_root51/_uninst directory in the V5.1 installation root before issuing the uninstall command.The command file is located in the install_root51/_uninst directory on a Linux or UNIX-based platform, and in the install_root51\_uninst directory on a Windows system.

      For example, use this command to change directories on a Linux platform: 

      cd /opt/WebSphere/AppServer51/_uninst

    3. Issue the uninstall command.The command file is named uninstall for Linux and UNIX-based platforms and Uninstall.exe on Windows platforms.

      On Windows platforms, call the Uninstall.exe command: 

      install_root51\_uninst\Uninstall.exe

      Call the program directly from the install_root51\_uninst directory. For example, if the installation root is C:\WebSphere\AppServer51, issue the following command: 

      C:\WebSphere\AppServer51\_uninst> Uninstall.exe

      On Linux and UNIX-based platforms, issue the uninstall command from the install_root/_uninst directory: 

      uninstall

    4. Use the uninstaller wizard panel to keep the embedded messaging feature code installed.When the V5.1 uninstaller wizard displays a panel that prompts you whether to uninstall the embedded messaging feature, clear the check box to leave the feature installed so that the V5.0.2 node can continue to use the code.

    5. After the uninstaller removes the V5.1 code, change directories to the install_root50/bin directory.

    6. Start the V5.0.2 deployment manager with the startManager command.

    7. Stop and restart the V5.0.2 Application Server.For example, run these commands from the install_root50/bin to recycle the server1 process and the nodeagent process on a Linux platform: 

      stopServer.sh server1

startNode.sh 

startServer.sh server1

    8. (Optional)   Uninstall V5.1 artifacts before reinstalling V5.1.Select a platform-specific procedure for completing the removal of the product: This step is required before you can reinstall the product into the same installation root directory.

 

Results

You can uninstall a base node that has the embedded messaging server and client feature.

 

What to do next

Return to Uninstalling the product.

Related tasks
Uninstalling in a migration scenario
Installing the product
Uninstalling manually