Learn how to clean a Solaris system if uninstallation of WebSphere® ESB fails.
After running the uninstallation program, go through these manual
steps to remove registry entries that can prevent you from reinstalling
the product into the original directory.
Before you begin
Before performing this procedure, ensure you have uninstalled WebSphere ESB using
the uninstallation wizard or silently, and that the procedure was
not completed successfully. If the procedure was successful, you do
not need to perform this task.
Determine the install_root directory
for the product so that you remove the correct product and produce
a clean system.
For details on default directory locations see Default installation directories for the product, profiles, and tools.
The
installation wizard and the Profile Management Tool let you specify
your own locations for installation root directories. Examine the
following files to determine the actual locations:
- The /opt/.ibm/.nif/.nifregistry file identifies the installation
root for all installed WebSphere ESB products;
it also looks for all WebSphere Application
Server products.
- The install_root/logs/manageprofiles/profile_name_create.log file
for each created profile identifies the installation location in the
stanza with the invokeWSProfile method.
Uninstalling the product leaves the
profile_root directory,
including the
profile_root/logs directory file, where
profile_root represents
the installation location of the profile. It leaves the
install_root/logs directory
as well.
About this task
Reinstalling the product into a new directory when files
remain from a previous installation can create a coexistence scenario.
However, you can delete all files and registry entries to completely
remove WebSphere ESB.
A clean system lets you reinstall the product into the original directory
without coexistence.
Important: Throughout this
procedure, steps address removing artifacts left after uninstallation
of bothWebSphere ESB and WebSphere Application Server
or WebSphere Application
Server Network Deployment. The WebSphere Application
Server product addressed is assumed to be the one underlying the installation
of WebSphere ESB.
Perform
the following procedure to produce a clean system.
Procedure
- Log on as the same user ID who installed the product.
- Use the kill command to stop all Java™ processes that are running.
If
you are running Java processes
that are not related to
WebSphere ESB or WebSphere Application Server
products and it is not possible to stop them, stop all
WebSphere ESB and WebSphere Application Server
product-related processes. Use the following command to determine
all processes that are running:
ps -ef | grep java
Stop all
WebSphere ESB and WebSphere Application Server
product-related processes with the
kill -9 java_pid_1 java_pid_2...java_pid_n command.
- Search for related packages. Issue the following
command to show packages for the WebSphere ESB and WebSphere Application Server
products (if no packages appear when using these commands, skip the next step):
pkginfo | grep WS
To narrow your query to search for
WebSphere ESB packages
only, type the following command:
pkginfo | grep WSEAA62
For example, after issuing the command
pkginfo
| grep WSEAA62, the following list of packages might be displayed:
application WSEAA62 IBM WebSphere Enterprise Service Bus
application WSEAA62LC LAP Component
WebSphere ESB, version
6.2, package names have a prefix of WSE and a suffix of 62. WebSphere Application Server
Network Deployment, version 6.1, package names have a prefix of WSB
or WSP and a suffix of 61. Do not remove packages for WebSphere ESB and WebSphere Application Server
products that you did not uninstall.
- Change directories to the directory where
package information is registered.
cd /var/sadm/pkg
- Issue the following command to remove any WebSphere ESB or WebSphere Application Server
product-related packages.
pkgrm packagename1 packagename2 packagename3 ...
Do not remove packages for WebSphere ESB and WebSphere Application Server
products that you did not uninstall.
Issue the following commands
from the
/var/sadm/pkg directory to search for and remove
any WebSphere Application
Server product-related packages that are registered in the
/var/sadm/pkg directory:
- Change directories to the correct directory: cd /var/sadm/pkg
- ls |grep WSB|xargs -i pkgrm -n {} for WebSphere Application Server products
- ls |grep WSC|xargs -i pkgrm -n {} for WebSphere Application Server Clients
- ls |grep WSP|xargs -i pkgrm -n {} for Web server plug-ins
for WebSphere Application
Server
- ls |grep WSE|xargs -i pkgrm -n {} for WebSphere ESB
Package names for Web server plug-ins for WebSphere Application Server are:
WSPAA61
WSPAA61AC
WSPAA61BC
WSPAA61CC
WSPAA61DC
WSPAA61FC
WSPAA61FB
WSPAA61GC
WSPAA61HC
If there is a problem removing the packages, remove
the related package directories in the
/var/sadm/pkg directory,
including the preremove files. For example, remove the following file
before issuing the
pkgrm -n WSBAA61 command:
/var/sadm/pkg/WSBAA61/install/preremove
- Remove any profile directories that are not located in
the installation root (install_root) directory.
To determine the locations of profile directories, first
use the wasprofile -listProfiles command to display
profile names. Then, to determine where profile directories are located,
use the wasprofile -getPath -profileName profile_name command,
where profile_name is the name
of the profile corresponding to a given directory.
- Remove the installation root directory. Type rm
-rf install_root to remove WebSphere ESB directories.
Ensure you specify the correct install_root for the product
you uninstalled. For example, if you uninstalled WebSphere ESBfrom
the default installation directory /opt/IBM/WebSphere/ESB, issue the following
command:
rm -rf /opt/IBM/WebSphere/ESB
Remove all of the profile directories as well.
- Edit the /opt/.ibm/.nif/.nifregistry file.
This file contains a one-line entry for each WebSphere ESB product
installation; and also has an entry for each WebSphere Application Server product installation.
You
can delete these files if there is just one line in each that identifies
the product that you removed. Otherwise, use a flat-file editor to
remove the line that identifies the installation root directory of
the product that you removed. Leave the other lines intact.
- Use the installRegistryUtils command to
examine the installation locations for all installed WebSphere ESB products
and remove the desired products from the install registry.
Results
This procedure results in having a clean system. You can
reinstall into the same directories now. A clean system has no trace
of a previously deleted installation.
What to do next
After you have cleaned your system, go to Installing the software to
choose an installation procedure.