This procedure cleans a Solaris system if uninstallation
of WebSphere Process Server fails. After running the uninstallation
program, these manual steps remove registry entries that can prevent
you from reinstalling the product into the original directory. If
you are not planning to reinstall, do not perform this task.
Before you begin
Before performing this procedure, ensure you
have uninstalled WebSphere Process Server using the Uninstallation Wizard
or silently, and that the procedure was not completely successful.
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.
Default directories are shown in Table 1:
Table 1. Planning table for
identifying actual location of product installationIdentifier |
Default directory location |
Actual location |
install_root |
/opt/IBM/WebSphere/ProcServer or /opt/IBM/WebSphere/AppServer |
|
profile_root |
/opt/IBM/WebSphere/ProcServer/profiles
/profile_name or /opt/IBM/WebSphere/AppServer/profiles
/profile_name A character space was added to these
entries to enable them to fit in the table cell. The actual entries
do not include a character space.
|
|
The Installation Wizard and the Profile
Wizard let you specify your own locations for installation root
directories. Examine the following files to determine the actual
locations:
- The ~/.WBIRegistry file identifies the
installation root for all installed WebSphere Process Server products;
the ~/.WASRegistry file, for all WebSphere Application
Server products. These files are located in the home directory of
the user ID from which the product was installed.
- The install_root/logs/wasprofile/wasprofile_create_profile_name.log file
for each created profile identifies the installation location in
the stanza with the <method>invokeWSProfile</method> tag.
Uninstalling
the product leaves the
profile_root directory, including
the
profile_root/logs directory with the
pcatLog<timestamp>.txt file,
where
profile_root represents the installation location of
the profile. It leaves the
install_root/logs directory
as well.
Why and when to perform 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 Process Server. 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 Process
Server 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 Process Server.
Perform the following procedure
to produce a clean system.
Steps for this task
- Log on as root.
- Use the kill command to kill all Java processes
that are running.
If you are running Java processes that are not related
to
WebSphere Process Server or WebSphere Application Server products
and it is not possible to stop them, stop all WebSphere Process
Server 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 Process Server 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
Process Server 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 Process Server packages
only, type the following command:
pkginfo | grep WSEAA60
For example, after issuing the command
pkginfo | grep WSEAA60,
the following list of packages might be displayed:
application WSEAA60AB Non-HPRepository
application WSEAA60BM BPCSamples
application WSEAA60BN BPCSamples.ismp.component
application WSEAA60BO Bpc.ismp.component
application WSEAA60BP Bpc
application WSEAA60CA WBICoreSamples.ismp.component
application WSEAA60CC WBICore.ismp.component
application WSEAA60CE CEI
application WSEAA60CI CEI.ismp.component
application WSEAA60CM CEISamples
application WSEAA60CS WBICoreSamples
application WSEAA60EMSCO CEISamples.ismp.component
application WSEAA60JC Javadocs.ismp.component
application WSEAA60JD Javadocs
application WSEAA60LC LAP Component
application WSEAA60SA Samples
application WSEAA60SC WBIServerSamples.ismp.component
application WSEAA60SS WBIServerSamples
application WSEAA60WC WBICore
application WSEAA60WS WBIServer
WebSphere Process Server package names have a prefix of WSE and
a suffix of 60. WebSphere Application Server Network Deployment,
version 6.0, package names have a prefix of WSB or WSP and a suffix
of 60. Do not remove packages for WebSphere Process Server 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 Process
Server or WebSphere Application Server product-related packages.
pkgrm packagename1 packagename2 packagename3 ...
Do not remove packages for WebSphere Process Server 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 Process
Server products
Package names for Web server plug-ins for WebSphere Application
Server are:
WSPAA60
WSPAA60AC
WSPAA60BC
WSPAA60CC
WSPAA60DC
WSPAA60FC
WSPAA60FB
WSPAA60GC
WSPAA60HC
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 WSBAA60 command:
/var/sadm/pkg/WSBAA60/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
Process Server directories. Ensure you specify the correct install_root for
the product you uninstalled. For example, if you uninstalled WebSphere
Process Server from the default installation directory /opt/IBM/WebSphere/ProcServer,
issue the following command:
rm -rf /opt/IBM/WebSphere/ProcServer
Remove all of the profile directories as well.
- Edit the .WBIRegistry and .WASRegistry files.
These files are located in the home directory of the user
ID from which the product was installed.
The .WBIRegistry file contains a one-line entry for
each WebSphere Process Server product installation; the .WASRegistry file,
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. Do not delete the .WBIRegistry and .WASRegistry files
unless you removed all of the installations listed in the files.
Result
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 product to choose an installation procedure.