Learn how to clean a Linux® 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
and 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,
where
profile_root represents the installation
location of the profile. It also leaves the
install_root/logs directory.
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 both WebSphere 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.
- 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:
rpm -qa | grep WS
To narrow your query to search for
WebSphere ESB packages
only, type the following command:
rpm -qa | grep WSEAA62
For example, after issuing the command
rpm
-qa | grep WSEAA62, the following package might be displayed:
WSEAA62LicensingComponent-6.2-0
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.
- If there are packages to delete, type rpm -e packagename to
remove any packages for the product that you uninstalled.
Alternatively, you can search for packages to verify
that every item in the list is something to delete:
rpm -qa | grep WSEAA62
If the list contains packages that you intend to delete
and no others, remove all of the packages with the following command:
rpm -qa | grep WSEAA62 | xargs rpm -e
If there is a problem with package dependencies, you
can use the following command to remove the packages:
rpm -e packagename --nodeps --justdb
The nodeps option skips the dependency
check. The justdb option updates only the package
database, and not the file system. Using only the nodeps option
can cause a failure in package removal if there is any mismatch in
the dependent file system (files and directories).
- 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 ESB from
the default installation directory /opt/ibm/WebSphere/ESB, issue the following
command:
rm -rf /opt/ibm/WebSphere/ESB
- Edit the vpd.properties file to remove
the entries for WebSphere ESB and WebSphere Application Server
or WebSphere Application
Server Network Deployment.
The file
is located in the installation directory of the operating system,
such as the
root directory. Remove all entries for
the installation of
WebSphere ESB that
you have uninstalled. Each
WebSphere ESB entry
starts with the characters
WSE, followed by numbers
representing the release number, and on the same line will have the
install_root path
corresponding to the installation you have uninstalled. (Each entry
is on a single line if the file is displayed in a text editor with
word wrap turned off.) For example, the line
WSEAA62|6|2|0|0|6.2.0.0|2=IBM WebSphere Enterprise Service Bus|
IBM Enterprise Service Bus|IBM Enterprise Service Bus V6.2|
IBM|http://www.ibm.com|6.2.0.0|
C:\Program Files\IBM\WebSphere\ESB|0|0|1|WSEAA62|6|2|0|0|6.2.0.0|2|0|
false|"properties/version/_uninst.wbi" "uninstall.jar" "uninstall.dat" "
"|true|3|WSEAA62|6|2|0|0|6.2.0.0|2
corresponds to the
WebSphere ESB that
was installed in the directory
C:\Program Files\IBM\WebSphere\ESB.
Note: This text appears in several lines in this document for
formatting purposes but would be a single line in the vpd.properties file.
Each WebSphere Application Server
or WebSphere Application
Server Network Deployment entry in the vpd.properties file
has a similar format. For information about these entries to help
you determine which to delete, and for more information about the vpd.properties file,
refer to the topic vpd.properties file in the WebSphere Application Server Network Deployment,
version 6.1 information center.
Do not delete or rename the vpd.properties file
because the InstallShield MultiPlatform (ISMP) program uses it for
other products that it installs. If the WebSphere ESB or WebSphere Application Server
product that you are uninstalling is the only product with entries
in the vpd.properties file, you can delete this
file.
- Edit the /opt/.ibm/.nif/.nifRegistry file.
This file is located in the home directory of the user ID
from which the product was installed.
The /opt/.ibm/.nif/.nifRegistry file
contains a one-line entry for each WebSphere ESB product
installation and also an entry, for each WebSphere Application Server product installation.
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.