Manually uninstalling on an AIX system
This procedure uninstalls a WAS product from an AIX system. After running the uninstaller program, manual steps remove log files and registry entries that can prevent you from reinstalling the product into the original directory. If you are not planning to reinstall, do not uninstall manually.
Before you begin
The uninstaller program removes all profiles, including all of the configuration data and applications in each profile. Before you start the uninstall procedure, back up the config folder, the installableApps folder, and the installedApps folder of each profile, if necessary. See Using command line tools for a description of managing configuration files. Back up all applications that are not stored in another location.
Determine the installation root directory for the product so that you remove the correct product and produce a clean system.
Overview
Reinstalling the product into a new directory when files remain from a previous installation can create a coexistence scenario. However, one can delete all files and registry entries to completely remove a WAS product. A clean system lets you reinstall the product into the original directory without coexistence.
Default directories are shown in the following planning table:
Identifier Directory Actual location install_root /usr/IBM/WebSphere/AppServer profiles_install_root /usr/IBM/WebSphere/AppServer/profiles plug-ins_install_root /usr/IBM/WebSphere/Plugins The Installation wizard and the Profile creation wizard let you specify your own locations for installation root directories. Examine the following files to determine the actual locations:
- The ~/.WASRegistry file identifies the installation root for all installed WAS products.
- The install_root/logs/wasprofile/wasprofile_create_profile.log file for each created profile identifies the installation location in the stanza with the <method>invokeWSProfile</method> tag.
Uninstalling the product leaves the profiles_root/profile directory with the pctLog.txt file.
Perform the following procedure to produce a clean system.
Procedure
- Log on as root.
- Run the uninstaller program for the Web server plug-ins for WebSphere Application Server.
If a Web server is configured to run with the application server, uninstall the plug-ins to remove the configuration from the Web server. See Uninstalling the Web server plug-ins for WebSphere Application Server.
- Issue the uninstall command.
If you have already run the uninstaller program or if one cannot run the uninstaller program, simply skip this step.
install_root/_uninst/uninstallSee the description of the uninstall command for more information.
The Uninstaller wizard begins and displays the Welcome panel.
- Use the kill command to kill all Java processes that are running.
If running Java processes are not related to WAS products and it is not possible to stop them, stop all WAS product-related processes. Use the following command to determine all processes that are running
Stop all WebSphere Application Server-related processes with the kill -9 java_pid_1 java_pid_2...java_pid_n command.ps -ef | grep java- List WAS components that are installed.
Type the following command to search for related packages
lslpp -l| grep -i WSDo not remove packages for WebSphere Application Server products that you are not uninstalling. Version 6 package names have a prefix of WSB or WSP and a suffix of 60. WSC package names do not have a suffix of 60.
- Use the geninstall command to remove registry information for each component that displays in the list.
For example, issue the follow command to display packages with a prefix of WS
lslpp -l | grep -i WSThe system displays the list of matching packages
WSBAA60CoreRuntime 6.0.0.0 COMMITTED Installs the core product runIssue the follow command to remove the registry entry
geninstall -u WSBAA60CoreRuntime- Change directories to the /usr/IBM directory.
- Type rm -rf WebSphere to delete this WebSphere Application Server-related directory, but only if the AppServer directory is the only directory within the WebSphere directory. Delete the directory if the only products contained in the directory are products that you intend to delete.
- Edit the .WASRegistry file.
The file location is the home directory, ~/.WASRegistry.
The .WASRegistry file contains a one-line entry for each WAS product installation.
You can delete the file if there is just one line that identifies the product that you are removing. Otherwise, use a flat-file editor to remove the line that identifies the installation root directory of the product that you are removing. Leave the other lines intact. Do not delete the .WASRegistry file unless you are removing all of the installations listed in the file.
The following example shows a .WASRegistry file for a system with five installations:
/usr/IBM/WebSphere/AppServer /usr/IBM/ND/AppServer /usr/ExpressV6/IBM/WebSphere/AppServer /usr/ND/IBM/WebSphere/AppServer /usr/Express/IBM/WebSphere/AppServer- Run the odmclean.sh and aixclean.sh scripts.
Do not run the aixclean.sh script if the WebSphere MQ product is installed.
- Obtain the scripts from the technote document titled, Manual uninstall On AIX requires odmclean.sh and aixclean.sh on the WAS Support site.
- Edit the odmclean.sh script and replace every instance of the string /usr/WebSphere/AppServer with the actual installation root directory.
- Run the aixclean.sh script from the command line:
./aixclean.sh- Run the odmclean.sh script from the command line:
./odmclean.sh
Result
This procedure results in having a clean system. We can reinstall into the same directories now. A clean system has no trace of a previously deleted installation.
Example of displaying package names beginning with WS, for
WebSphere Application Server-related products==>lslpp -l | grep WS WSBAA60 6.0.0.0 COMMITTED ISMP installed entry WSBAA60AddBytesNonHP 6.0.0.0 COMMITTED ISMP installed entry WSBAA60CoreRuntime 6.0.0.0 COMMITTED Installs the core product run WSBAA60CoreRuntimeComponent WSBAA60Javadocs 6.0.0.0 COMMITTED Installs the public Java API WSBAA60JavadocsComponent 6.0.0.0 COMMITTED ISMP installed entry WSBAA60License 6.0.0.0 COMMITTED ISMP installed entry WSBAA60LicenseComponent 0.0.0.0 COMMITTED ISMP installed entry WSBAA60LicensingComponent 0.0.0.0 COMMITTED This bean will work with the WSBAA60Samples 6.0.0.0 COMMITTED Includes Samples with source WSBAA60SamplesComponent 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60DefineglobalconstantsComponent 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60DefinelocalvariablesComponent 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60LicensingComponent 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60Webserverplugins 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60WebserverpluginsComponent 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60AddBytes 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60gskit 6.0.0.0 COMMITTED ISMP installed entry... WSPAA60gskitComponent 6.0.0.0 COMMITTED ISMP installed entry...
What to do next
Go to Task overview: Installing to begin planning a new installation.