WAS Uninstall

 

Overview

WAS provides an uninstaller program, that removes registry entries, uninstalls the product, and removes all related features and products, such as plug-ins. The uninstall program does not delete any configuration files that are changed as the result of selecting installation options and does not delete log files. The uninstaller program leaves a readme file in the _uninst directory after it runs, to describe how to completely uninstall the product.

 

Uninstall Procedure

Here are some are instructions for re-installing WAS (WAS) Version 5.1 and WebSphere MQ. This is not official IBM documentation and is merely offered as a guide to how you might want to approach the re-install....

  1. Make a backup copy of the current configuration...

    • Shut down the nodes in the cluster but leave DeploymentManager running.

    • cd /opt/WebSphere/DeploymentManager/bin

    • backupConfig.sh -user username -password password 

      venus [8:52am] # backupConfig.sh -user username -password password
ADMU0116I: Tool information is being logged in file
           /opt/WebSphere/DeploymentManager/logs/backupConfig.log
ADMU5001I: Backing up config directory /opt/WebSphere/DeploymentManager/config
           to file
           /opt/WebSphere/DeploymentManager/bin/WebSphereConfig_2004-04-09.zip
ADMU0505I: Servers found in configuration...
ADMU0506I: Server name: dmgr
ADMU2010I: Stopping all server processes for node venusManager
ADMU0510I: Server dmgr is now STOPPED
ADMU5002I: 212 files successfully backed up
venus [8:54am] #

    • A file called WebSphereConfig_YYYY-MM-DD.zip (with YYYY, MM, DD being the year, month, day) will be created in the /opt/WebSphere/DeploymentManager/bin directory.

      Important: This file should then be copied OUT of this directory and kept in a safe place, as the /opt/WebSphere directory and everything underneath it will eventually need to be deleted to perform the upgrade.

  2. Remove messaging objects

    Before you uninstall the product, remove messaging objects such as queue connection factories and queue destinations from the configuration. If these objects are not removed prior to an uninstall, the messaging component detects that these objects still exist and, by design, will not uninstall itself.

    Check the mq_uninstall.log to verify the uninstall was clean.

    Even if all JMS resources, such as queue connection factories and queue destinations, are removed, or none are created, the messaging component still might not uninstall completely, which causes the reinstall of the product to fail. This failure is indicated by the following message in the mq_uninstall.log file:

    Return code from Publish And Subscribe uninstall was ERROR_INSTALL_FAILURE (1603)

    The messaging component may be still resident and usable, and the recommended resolution is to first try reinstalling WAS with messaging, in the same location as before, ignoring messages indicating that messaging is already installed, and to proceed normally unless you encounter problems.

  3. Uninstall IBM HTTP Server

    If you installed the IBM HTTP Server feature using the WAS installation wizard use the WAS uninstaller program to uninstall. If you uninstall HTTP Server using the HTTP Server uninstaller program, you cannot reinstall HTTP Server using the WAS installer program. Use the HTTP Server installer program to reinstall the product.

    If you uninstall the HTTP Server using the WAS uninstaller program, you can reinstall HTTP Server using the WAS installer program.

  4. Close all Web browser processes. Before uninstalling, verify that you have no open Web browsers that are accessing the administrative console. Otherwise, there is the potential for locked file errors as you uninstall.

  5. Stop the IBM HTTP Server and any related Java processes. Stop these processes only if the processes are running on the same machine as WAS.

  6. Stop all Java processes that are related to WAS products on the machine.

  7. Uninstall the WebSphere AppServer

    • cd /opt/WebSphere/AppServer/_uninst

    • Set the DISPLAY variable to export your X session back to your local machine (ie. setenv DISPLAY host:0.0)

    • uninstall

    • Follow the prompts to remove the product

  8. Uninstall the WebSphere Deployment Manager

    • cd /opt/WebSphere/DeploymentManager/_uninst

    • uninstall

    • Follow the prompts to remove the product

  9. Verify whether or not MQ is installed on the machine and if so, remove it...

    • pkginfo | grep -i mqm

      If it's installed, the output will look something like this... 

      venus [9:06am] # pkginfo | grep -i mqm
application mqm                  WebSphere MQ for Sun Solaris
venus [9:06am] #

    • Remove the package by running:

      pkgrm mqm

      ...and follow the prompts.

    • Perform another...

      pkginfo | grep -i mqm

      ...to confirm that it's been removed.

  10. When finished with steps 2 through 4 above, be able to perform a "pkginfo | grep -i sphere" and get NOTHING back.

  11. Since uninstalling the AppServer and DeploymentManager doesn't fully remove the /opt/WebSphere/AppServer and /opt/WebSphere/DeploymentManager directories, these directories should either be moved out of the way or removed altogether to make way for the new installation. If the directories are still there when you go to perform the 5.1 install, the installation will fail.

    • Either:

      mv /opt/WebSphere /opt/WebSphere.old

      or:

      rm -rf /opt/Websphere

  12. Install MQ Series 5.3, both client and server

  13. Re-create your MQ queues.

  14. Install WebSphere Deployment Manager 5.1, AppServer 5.1 and the latest Fixpacks.

    • Install WAS51 BASE first...

      launchpad.sh

      Follow the prompts to complete the install (If it allows you, do not install Embedded Messaging Client or Server)

    • Install WAS51 ND second...

      launchpad.sh

      Follow the prompts to complete the install

    • Install the Cumulative Fixpack 3 for both BASE and ND (this needs to be run twice, once for each of the products)

      updateWizard.sh

  15. Federate the nodes into your cluster...

    • On *EACH* of the nodes (do not try to federate more than one node at a time, you'll get errors) you'll be adding to the cluster, perform the following...

      cd /opt/WebSphere/AppServer/bin
      addNode.sh dmgr_host

  16. Restoring the initial configuration.

    • Make a backup copy of the current security.xml file...

      cd /opt/WebSphere/DeploymentManager/config/cells/venusNetwork
      cp security.xml security.xml.backup

    • Restore the original backup file...

      cd /opt/WebSphere/DeploymentManager/bin
      restoreConfig /path/to/your/backup_file.zip

    • Copy the security.xml.backup file you created in step 8a above over the top of the one that's now in...

      /opt/WebSphere/DeploymentManager/config/cells/venusNetwork

    • Start the DeploymentManager process: /opt/WebSphere/DeploymentManager/bin/startManager.sh

    • Security will need to be reconfigured via the console (during which point the new LTPA encryption information will be created for the new environment/server).

    • Recreate J2C aliases

  17. Once security has been configured, shut down the DeploymentManager and re-sync the nodes to that they all contain the proper configurations...

    • /opt/WebSphere/DeploymentManager/bin/stopManager.sh -username username -password password

    • On *ALL* of the app servers in the cluster, perform the following...

      cd /opt/WebSphere/AppServer/bin
      syncNode.sh dmgr_name

  18. Start the DeploymentManager...

    cd /opt/WebSphere/DeploymentManager/bin
    startManager.sh

    The uninstall wizard can uninstall WAS, the HTTP server, and embedded messaging.

    To execute..

    $WAS_HOME/_uninst/uninstall

    After uninstalling a WAS product, delete the installation root directory before reinstalling into the same directory.

    Here are some examples on how to uninstall silently.

    uninstall -silent -W MQUninstallSelectionSequence.active= "false"
    uninstall -silent -W MQUninstallSelectionSequence.active= "true"
    uninstall -silent -W MQUninstallSelectionPanel.uninstallClient= "false"
    uninstall -silent -W MQUninstallSelectionPanel.uninstallClient= "true"
    uninstall -silent -W MQUninstallSelectionPanel.uninstallServer= "false"
    uninstall -silent -W MQUninstallSelectionPanel.uninstallServer= "true"

    The return code from the uninstaller program is "1" to indicate success; any other response code indicates failure. If the return code indicates an error examine $WAS_HOME/logs/uninstlog.txt, and then uninstall manually.

    uninstall -silent -W MQUninstallSelectionPanel.uninstallServer= "true"
    return_code=`echo $?`
    echo "Return code is $return_code

 

Manually uninstalling on Solaris platforms

  1. Stop all Deployment Manager, node manager, and WAS processes.

  2. Determine if any WebSphere java processes are still running... 

    ps -ef | grep java

  3. Kill any stray Java processes

    killall -9 java

  4. Halt any running WebSphere MQ queue managers.

    dspmq
    endmqm -i queue_manager
    ipcs -a
    ipcrm -[qms] [ID]

  5. Stop any MQ processes that are running.

    kill -9 amq_pid_1 amq_pid_2 ... amq_pid_n

  6. Search for WAS, embedded messaging, and MQ packages:

    pkginfo | grep WS
    pkginfo | grep wemps
    pkginfo | grep mqm

  7. To remove any WAS-related packages:

    pkgrm packagename1 packagename2 packagename3 ...

    Remove mqm last or you will not be able to remove any other embedded messaging feature packages. You would have to reinstall the embedded messaging feature to remove the packages.

    To remove the embedded messaging feature from your system

    pkgrm wemps mqjava mqm-upd04 mqm

  8. Alternatively, you can type the following commands to search for and remove any WAS product-related packages: 

    ### Base WAS product
ls | grep WSB | xargs -i pkgrm -n {} 

### WAS Java client
ls  | grep WSC | xargs -i pkgrm -n {} 

### WebSphere embedded messaging publish and subscribe function
ls  | grep wemps | xargs -i pkgrm -n {} 

### IBM WebSphere MQ
ls  | grep mqjava | xargs -i pkgrm -n {} 

### IBM WebSphere MQ
ls  | grep mqm | xargs -i pkgrm -n {}

  9. A known problem in ISMP causes ISMP to rename packages from beginning with WS to beginning with ISWS. Search for and remove ISWS packages as well... 

    ### Base WAS product
ls | grep ISWSB | xargs -i pkgrm -n {} 

### WAS Java client
ls | grep ISWSC | xargs -i pkgrm -n {} 

### WebSphere embedded messaging publish and subscribe function
ls | grep wemps | xargs -i pkgrm -n {} 

### IBM WebSphere MQ
ls | grep mqjava | xargs -i pkgrm -n {} 

### IBM WebSphere MQ
ls | grep mqm | xargs -i pkgrm -n {}

  10. If there is a problem removing the packages, remove the related package directories in /var/sadm/pkg.

  11. To remove WAS directories...

    rm -rf /opt/WebSphere/AppServer/

  12. To remove embedded messaging data:

    rm -fr /var/wemps /opt/wemps

  13. Delete the IBM HTTP Server directory.

    rm -rf IBMHttpServer

  14. To remove embedded messaging...

    rm -fr /var/mqm /opt/mqm

    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.

 

Example package names for system with base 

application ISWSBIH1A            ihsComponent
application ISWSBJD9A            javaCommonConfigComponent
application ISWSBJD9A.2          javaCommonConfigComponent
application ISWSBLA1A            logAnalyzerComponent
application ISWSBLAAA            LogAnalyzer
application WSBAA                WAS
application WSBAAAA              Application And Assembly Tools
application WSBAC1AA             adminConsoleFilesComponent
application WSBACAA              Admin Console
application WSBADAA              Admin
application WSBAS1AA             adminScriptingFilesComponent
application WSBASAA              Admin Scripting
application WSBAT1AA             applicationAssemblyToolComponent
application WSBATAA              Application Assembly Tool
application WSBAU1AA             antUtilityComponent
application WSBAUAA              Ant Utility
application WSBCO1AA             commonFiles
application WSBCO4AA             pbwServerConfigWithMQGood
application WSBCO5AA             IsmpLauncherComponent
application WSBCOAA              commonFeature
application WSBDM1AA             DCMStdComponent
application WSBDMAA              Dynamic Cache Monitor
application WSBDT1AA             deployToolComponent
application WSBDTAA              Deploy Tool
application WSBES1AA             messagingSampleFileComponentBean
application WSBESAA              mqSeriesSamples
application WSBGK2AA             gskitUnixComponent
application WSBGK3AA             gskit4SolarisComponent
application WSBGKAA              gskitFeature
application WSBIHAA              ihsFeature
application WSBJA1AA             javadocComponent
application WSBJAAA              Javadoc
application WSBJD4AA             javaSolarisComponent
application WSBJD7AA             javaUninstallComponent
application WSBJDAA              Java
application WSBMQ1AA             mqSeriesSetupFileComponent
application WSBMQ2AA             mqSeriesBinComponent
application WSBMQ3AA             mqSeriesLibFilesComponent
application WSBMQAA              MQSeries
application WSBMS6AA             mqSeriesSunConfig
application WSBMSAA              mqSeriesServer
application WSBPL1AA             component8
application WSBPLAA              Plugins
application WSBPS1AA             perfServletComponent
application WSBPSAA              Performance Servlet
application WSBPTAA              PerformanceAndAnalysisTools
application WSBSM1AA             samplesComponent
application WSBSMAA              Samples
application WSBSR1AA             serverStdComponent
application WSBSR4AA             serverConfigWithoutSamplesComponent
application WSBSRAA              Server
application WSBTV1AA             tivoliViewerComponent
application WSBTVAA              TivoliPerformanceViewer

 

Example package names for system with base and network deployment

application IBMHTTPSV      IBM HTTP Server
application ISIHS.bas      HTTPServer base
application ISIHS.con      component23
application ISIHS.htt      feature13
application ISIHS.ins      component26
application ISIHS.ssl      component57
application ISWSBIH1A      ihsComponent
application ISWSBJD9A      javaCommonConfigComponent
application ISWSBLA1A      logAnalyzerComponent
application ISWSBLAAA      LogAnalyzer
application ISWSNJD9A      javaCommonConfigComponent
application ISWSNMQ1A      mqClientFiles
application ISWSNMQAA      mqFeature

application WSBAA51        WAS
application WSBAAAA51      Application And Assembly Tools
application WSBAC1AA51     adminConsoleFilesComponent
application WSBACAA51      Admin Console
application WSBADAA51      Admin
application WSBAS1AA51     adminScriptingFilesComponent
application WSBASAA51      Admin Scripting
application WSBAU1AA51     antUtilityComponent
application WSBAUAA51      Ant Utility
application WSBCO1AA51     commonFiles
application WSBCO5AA51     IsmpLauncherComponent
application WSBCOAA51      commonFeature
application WSBDM1AA51     DCMStdComponent
application WSBDMAA51      Dynamic Cache Monitor
application WSBDT1AA51     deployToolComponent
application WSBDTAA51      Deploy Tool
application WSBES1AA       messagingSampleFileComponentBean
application WSBESAA        mqSeriesSamples
application WSBGK2AA51     gskitUnixComponent
application WSBGK3AA51     gskit4SolarisComponent
application WSBGKAA51      gskitFeature
application WSBIHAA51      ihsFeature
application WSBJA1AA51     javadocComponent
application WSBJAAA51      Javadoc
application WSBJD4AA51     javaSolarisComponent
application WSBJD7AA51     javaUninstallComponent
application WSBJDAA51      Java
application WSBMC4AA       mqSeriesClientUnixInstall
application WSBMQ1AA       mqSeriesSetupFileComponent
application WSBMQ2AA       mqSeriesBinComponent
application WSBMQ3AA       mqSeriesLibFilesComponent
application WSBMQAA        MQSeries
application WSBMS4AA       mqSeriesUnixInstall
application WSBMS6AA       mqSeriesSunConfig
application WSBMSAA        mqSeriesServer
application WSBPL1AA51     component8
application WSBPLAA51      Plugins
application WSBPS1AA51     perfServletComponent
application WSBPSAA51      Performance Servlet
application WSBPTAA51      PerformanceAndAnalysisTools
application WSBSM1AA51     samplesComponent
application WSBSMAA51      Samples
application WSBSR1AA51     serverStdComponent
application WSBSR4AA51     serverConfigWithoutSamplesComponent
application WSBSRAA51      Server
application WSBTV1AA51     tivoliViewerComponent
application WSBTVAA51      TivoliPerformanceViewer
application WSNAA51        WebSphere Network Deployment
application WSNCF1AA51     configFiles
application WSNCF4AA51     configSunLinuxWithMQComponent
application WSNCFAA51      Config
application WSNCO1AA51     commonFiles
application WSNCO2AA51     IsmpLauncherComponent
application WSNCOAA51      commonFeature
application WSNJD4AA51     javaSolarisComponent
application WSNJDAA51      Java
application WSNSR1AA51     serverStdComponent
application WSNSRAA51      Server
application WSNUR1AA51     uddiComponent
application WSNURAA51      UDDI
application WSNWG1AA51     wsgwComponent
application WSNWGAA51      Web Services Gateway
application WSNWSAA51      Web Services

application gsk4bas        gsk4bas
application gsk7bas        Certificate and SSL Base Runtime (gsk7bas)
application mqm            WebSphere MQ for Sun Solaris
application mqm-upd04      WebSphere MQ for Sun Solaris 2 - U486877
application wemps          WebSphere Embedded Messaging Publish and Subscribe Edition

 

Uninstall applications using wsadmin.sh

  1. Invoke the AdminApp object commands interactively, in a script, or use the wsadmin -c command from an operating system command prompt.

  2. Issue the following command...

    Using Jacl 

    $AdminApp uninstall application1

    Using Jython 

    AdminApp.uninstall('application1')

Uninstalling an application removes it from the WAS configuration and from all the servers that the application was installed on. The application binaries EAR(file contents) are deleted from the installation directory. This occurs when the configuration is saved for single server WAS editions or when the configuration changes are synchronized from deployment manager to the individual nodes for network deployment configurations.