Manually uninstalling on AIX platforms

This task describes how to uninstall the product on an AIX platform.

Before you begin

Use the following procedure to remove all remnants of a WebSphere Application Server product. This produces a clean system that allows you to reinstall the product. Before you begin, verify that you are removing only the product instance that you intend to remove and not coexisting products, or products that you might have migrated and do not intend to delete. It is important to know the installation root directory for the product instance that you are removing.

Why and when to perform this task

Use this procedure to uninstall WebSphere Application Server products. Uninstall the products in the following sequence when you are uninstalling more than one product:

  1. [5.0 only][Version 5.0.1][Version 5.0.2]WebSphere Application Server Enterprise on Network Deployment
  2. WebSphere Application Server Network Deployment
  3. [5.0 only][Version 5.0.1][Version 5.0.2]WebSphere Application Server Enterprise on the base product
  4. WebSphere Application Server (base product)

One of the ways that this procedure completely uninstalls the product is by completely deleting the installation root directory for the product. References to the directory are abbreviated install_root in some of the steps. The default install_root for WebSphere Application Server is the /usr/WebSphere/AppServer directory.

The default install_root for Network Deployment is the /usr/WebSphere/DeploymentManager directory.

Steps for this task

  1. Use the kill -9 java_pid command to kill each Java process that is running.

    If there are Java processes running that are not related to WebSphere Application Server products, and it is not possible to stop them, stop all WebSphere Application Server product-related processes. Use the following command to determine all processes that are running:

    ps -ef | grep java
    Stop all WebSphere Application Server-related processes with the kill -9 java_pid_1 java_pid_2...java_pid_n command.

  2. Halt any running MQ queue managers.
    1. Type dspmq to show the state of any queue managers.
    2. Type endmqm -i for each running queue manager.
    3. Type $ ipcs -a to check for any IPCs.
    4. Type $ ipcrm -[qms] [ID] to delete the IPCs.
  3. Type kill -9 amq_pid_1 amq_pid_2 ... amq_pid_n to stop any MQ processes that are running.
    You can use a ps -e | grep #AMQ_COMMAND#' command structure to specify the command for amq to find each amq pid.
  4. Search for related packages.
    Either use smit to remove packages, or search for and remove packages manually:
    • Type smit to clean up remnants.
      1. Click Software Installation and Maintenance.
      2. Click Software Maintenance and Utilities.
      3. Click Remove Installed Software.
      4. Click LIST by Software name.
      5. Search for packages that contain the words IBM or WS to identify all WebSphere Application Server product-related packages, including those that belong to IBM HTTP Server and the embedded messaging feature, which is based on IBM WebSphere MQ technology.
      6. Change the PREVIEW ONLY option to NO.
      7. Click OK.
    • Manually search for, and remove packages that are only in the instance that you intend to delete.

      Do not remove IBM WebSphere MQ packages if you have installed IBM WebSphere MQ as a separate product.

      Do not remove embedded messaging packages if you intend to leave the embedded messaging feature installed on the machine.

      If you do intend to remove WebSphere MQ or embedded messaging packages, include them in the commands you are running to remove packages. For example, type these commands to search for, and remove related packages:

      1. Search for related packages:
        1. lslpp -l | grep WS to show packages for WebSphere Application Server products and the IBM HTTP Server product
        2. lslpp -l | grep wemps to show packages related to the embedded messaging feature or to IBM WebSphere MQ.
        3. lslpp -l | grep mqjava to show packages related to the embedded messaging feature or to IBM WebSphere MQ.
        4. lslpp -l | grep mqm to show packages related to the embedded messaging feature or to IBM WebSphere MQ.

          You can also run the following command from root to remove the embedded messaging feature from your system:

          installp -u wemps mqjava mqm
          Reply y[es] to all prompts.

          However, do not remove any mqm or mqjava packages if you have installed IBM WebSphere MQ separately or if you have other WebSphere Application Server products that use the embedded messaging feature.

        The examples below show typical package names that might appear on a system with the base WebSphere Application Server product.

        If no packages appear when using these commands, skip the next step.

      2. Type smitty remove packagename1 packagename2 packagename3 ... to remove any WebSphere Application Server-related packages. Do not remove packages for any products that you intend to keep. Generally, you can identify packages that belong to V5.1 by the 51 on the end of WSB packages and WSN packages. However, WSBM and WSNM packages are for the embedded messaging feature and do not include the 51 on the end as an identifier.

        Do not remove IBM WebSphere MQ packages if you have installed IBM WebSphere MQ as a separate product, or if you have installed the embedded messaging feature and other product instances are using the feature.

        Do not remove IBM WEMPS packages unless you are certain that there is no embedded messaging data to preserve.

  5. Change the directory to the usr directory.
  6. Type rm -rf WebSphere to delete this WebSphere Application Server-related directory, if the only subdirectories are the AppServer and DeploymentManager directories and if the only product instances they contain are those that you intend to delete.
  7. Change directory to the usr/opt directory.
  8. Type rm -rf wemps to delete the embedded messaging feature directory if you are certain that there is no embedded messaging data to preserve.
    If you have other instances of WebSphere Application Server products on the same machine, and if they use the embedded messaging feature, do not remove the embedded messaging packages or directories.
  9. Change the directory to the /usr directory.
  10. Type rm -rf IBMHttpServer to delete the IBM HTTP Server directory.
  11. If you do not have IBM WebSphere MQ installed as a separate product on this machine, type rm -rf mqm to delete the embedded messaging feature directory if you are certain that there is no embedded messaging data to preserve.
    If you have other instances of WebSphere Application Server products on the same machine, and if they use the embedded messaging feature, do not remove the embedded messaging packages or directories.

    If you installed IBM WebSphere MQ as a separate product on this host to use as the messaging provider, and if you do not want to continue using WebSphere MQ, you can uninstall the product as described in the WebSphere MQ information.

  12. Edit the vpd.properties file.
    Certain situations require you to edit the vpd.properties file before reinstalling a WebSphere Application Server product. Edit the vpd.properperties file to remove entries for the WebSphere Application Server product that you are uninstalling and to remove entries for any of its features.

    Do not delete or rename the vpd.properties file because the InstallShield for MultiPlatforms (ISMP) program uses it for other products that it installs. If the vpd.properties file has no other entries, you can delete the file.

Results

When you finish, the product is completely uninstalled. You are now ready to reinstall. Reinstalling successfully into the same directory is the final indicator of success in removing the original product.

Example

Example of displaying package names beginning with mqm, for the embedded messaging feature

==>lslpp -l | grep mqm

  mqm.base.runtime           5.3.0.1  COMMITTED  WebSphere MQ Runtime for
  mqm.base.sdk               5.3.0.1  COMMITTED  WebSphere MQ Base Kit for
  mqm.client.rte             5.3.0.1  COMMITTED  WebSphere MQ Client for AIX
  mqm.java.rte               5.3.0.1  COMMITTED  WebSphere MQ Java Client and
  mqm.msg.De_DE              5.3.0.1  COMMITTED  WebSphere MQ Messages - German
  mqm.msg.Es_ES              5.3.0.1  COMMITTED  WebSphere MQ Messages -
  mqm.msg.Fr_FR              5.3.0.1  COMMITTED  WebSphere MQ Messages - French
  mqm.msg.It_IT              5.3.0.1  COMMITTED  WebSphere MQ Messages -
  mqm.msg.Ja_JP              5.3.0.1  COMMITTED  WebSphere MQ Messages -
  mqm.msg.Zh_CN              5.3.0.1  COMMITTED  WebSphere MQ Messages -
  mqm.msg.Zh_TW              5.3.0.1  COMMITTED  WebSphere MQ Messages -
  mqm.msg.de_DE              5.3.0.1  COMMITTED  WebSphere MQ Messages - German
  mqm.msg.en_US              5.3.0.1  COMMITTED  WebSphere MQ Messages - U.S.
  mqm.msg.es_ES              5.3.0.1  COMMITTED  WebSphere MQ Messages -
  mqm.msg.fr_FR              5.3.0.1  COMMITTED  WebSphere MQ Messages - French
  mqm.msg.it_IT              5.3.0.1  COMMITTED  WebSphere MQ Messages -
  mqm.msg.ja_JP              5.3.0.1  COMMITTED  WebSphere MQ Messages -
  mqm.msg.ko_KR              5.3.0.1  COMMITTED  WebSphere MQ Messages - Korean
  mqm.msg.pt_BR              5.3.0.1  COMMITTED  WebSphere MQ Messages -
  mqm.msg.zh_CN              5.3.0.1  COMMITTED  WebSphere MQ Messages -
  mqm.msg.zh_TW              5.3.0.1  COMMITTED  WebSphere MQ Messages -
  mqm.server.rte             5.3.0.1  COMMITTED  WebSphere MQ Server

Example of displaying package names beginning with wemps, for the embedded messaging feature

==>lslpp -l | grep wemps

wemps.base.runtime         2.1.0.0  COMMITTED  WebSphere Embedded Messaging

Example of displaying package names beginning with WS, for WebSphere Application Server-related products

==>lslpp -l | grep WS

  WSBAA                      5.0.0.0  COMMITTED  ISMP installed entry
  WSBAAAA                    5.0.0.0  COMMITTED  Installs tools for assembly
  WSBAC1AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBACAA                    5.0.0.0  COMMITTED  Includes adminconsole.ear, the
  WSBADAA                    5.0.0.0  COMMITTED  Installs the Administrative
  WSBAS1AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBASAA                    5.0.0.0  COMMITTED  Includes wsadmin, the
  WSBAT1AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBATAA                    5.0.0.0  COMMITTED  Includes a GUI-based tool for
  WSBAU1AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBAUAA                    5.0.0.0  COMMITTED  Includes Apache ANT, a
  WSBCO1AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBCO4AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBCO5AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBCOAA                    5.0.0.0  COMMITTED  ISMP installed entry
  WSBDT1AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBDTAA                    5.0.0.0  COMMITTED  Includes a command-line
  WSBES1AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBES3AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBESAA                    5.0.0.0  COMMITTED  Includes samples for
  WSBGK2AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBGKAA                    5.0.0.0  COMMITTED  ISMP installed entry
  WSBIHAA                   1.3.28.0  COMMITTED  Installs an Apache-powered Web
  WSBIHAB                   1.3.28.0  COMMITTED  ISMP installed entry
  WSBJA1AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBJAAA                    5.0.0.0  COMMITTED  Installs WebSphere public
  WSBJD3AA                   1.3.1.0  COMMITTED  ISMP installed entry
  WSBJD7AA                   1.3.1.0  COMMITTED  ISMP installed entry
  WSBJD9AA                   1.3.1.0  COMMITTED  ISMP installed entry
  WSBJDAA                    1.3.1.0  COMMITTED  ISMP installed entry
  WSBLA1AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBLAAA                    5.0.0.0  COMMITTED  Includes a graphical utility
  WSBMQ1AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBMQ2AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBMQ3AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBMQAA                    5.0.0.0  COMMITTED  Installs Java Messaging
  WSBMS2AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBMS4AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBMS5AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBMSAA                    5.0.0.0  COMMITTED  Includes JMS
  WSBPL1AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBPLAA                    5.0.0.0  COMMITTED  Installs plugins to configure
  WSBPTAA                    5.0.0.0  COMMITTED  Installs tools for performance
  WSBSM1AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBSMAA                    5.0.0.0  COMMITTED  Includes samples, including
  WSBSR1AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBSR5AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBSR6AA                   5.0.0.0  COMMITTED  ISMP installed entry
  WSBSRAA                    5.0.0.0  COMMITTED  Installs the application
  

What to do next

After uninstalling the product, see Installing WebSphere Application Server products to begin planning your next installation.

Related tasks
Uninstalling manually
Uninstalling when the embedded messaging client feature is installed



Searchable topic ID:   tins_uninstallUnix
Last updated: Jun 21, 2007 4:55:42 PM CDT    WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_uninstallUnix.html

Library | Support | Terms of Use | Feedback