Uninstalling V5.0.2 when the embedded messaging client feature is installed

This task describes how to uninstall the Network Deployment product or a federated base WebSphere Application Server, Version 5.0.2 product when the product has the embedded messaging client feature.

 

Overview

Uninstalling a V5.0.x node that has the embedded messaging client feature affects all other nodes that also use the feature. The uninstaller program on V5.0.x does not give you the option of leaving the client feature installed when you uninstall a product. However, you can rename the install_root/_uninst/mq directory to keep the code for the embedded messaging client feature installed when you uninstall the product.

Two alternatives exist for preserving the embedded messaging client code:

• Renaming the _uninst/mq directory before uninstalling the V5.0.2 product

  If you rename the _uninst/mq directory before uninstalling the V5.0.2 product, you do not have to reinstall the embedded messaging client feature because you avoid uninstalling the client. Renaming the directory is the recommended method whenever possible.

• Reinstalling the embedded messaging client code after uninstalling the V5.0.2 product

  If you uninstall V5.0.2 without renaming the _uninst/mq directory, you also uninstall the embedded messaging client code. You can recover by reinstalling the embedded messaging client feature. The general procedure is to uninstall V5.0.2 and to reinstall the client feature from the V5.1 product installation image, which is usually the product CD-ROM. You can also reinstall the client feature from the V5.0.2 product installation image, which is usually where you downloaded and unzipped Fix Pack 2. However, you might have a product CD-ROM for V5.0.2 on some platforms.

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. (Optional)   Rename the install_root/_uninst/mq directory to prevent uninstalling the embedded messaging client feature, uninstall the product, and rename the directory to its original name.

   1. Rename the install_root/_uninst/mq directory to prevent uninstalling the embedded messaging client feature.

   2. Follow the normal procedure for uninstalling the V5.0.2 deployment manager or federated base node:

      1. Follow the normal procedure for uninstalling a V5.0.2 deployment manager node.

      2. Follow the normal procedure for uninstalling the V5.0.2 federated or unfederated node.

   3. Rename the install_root/_uninst/mq directory to its correct name.

3. (Optional)   Reinstall the embedded messaging client feature on a Windows platform.You do not have to reinstall the embedded messaging client if you renamed the install_root\_uninst\mq directory as described in the earlier step.

   1. Locate the V5.1 product CD-ROM.

   2. Identify the original installation location of the embedded messaging client feature on a Windows machine. Use the administrative console of the V5.1 product to examine the value of the MQ_INSTALL_ROOT variable in Environment > Manage WebSphere variables.

   3. (Optional)   Issue the command to reinstall the embedded messaging client code on a Windows platform:

      source_path\wmsetup /installc parm1 parm2 parm3 parm4

      source_path

      The fully qualified file path to the wmsetup command, either on disk or in the \messaging\client directory on the product CD-ROM.

      parm1

      The file path where the embedded messaging feature was originally installed, which is by default C:\Program Files\IBM\WebSphere MQ on a Windows platform.

      parm2

      The source location of embedded messaging software, such as the \messaging\client directory on the product CD-ROM.

      parm3

      The path and file name for recording log messages.

      parm4

      A code that represents the installation language. For example, 1033 for US English.

      For example, you can use the following command by entering it all on one line:

      E:\WASTEST\messaging\client\Setup\wmsetup /installc   
           C:\Program Files\IBM\WebSphere MQ   
           I:\Windows\messaging\client  
           C:\temp\mq_install.log   
           1033

4. Issue the command to reinstall the embedded messaging client code on a Linux or UNIX-based platform.You do not have to reinstall the embedded messaging client if you renamed the install_root/_uninst/mq directory as described in the earlier step.Command to use on a Linux or UNIX-based platform:

   source_path/wmsetup installc logfile

   source_path

   The fully qualified file path to the wmsetup command, either on disk or in the /messaging/client directory on the product CD-ROM.

   logfile

   The path and file name for recording log messages.

   For example:

   ./wmsetup installc /tmp/mq_install.log

 

Results

You can uninstall a V5.0.2 node that uses the embedded messaging client feature without affecting other nodes that also use the client feature.

 

What to do next

Return to Uninstalling the product.

---

Uninstalling when the embedded messaging client feature is installed
Installing the product
Uninstalling manually
    

 

---