Uninstall the feature pack product files, leaving the application
server product intact.
Before you begin
The uninstall command calls
the uninstaller program that is created during installation. The uninstaller
program is customized for each product installation, with specific disk locations
and routines for removing installed features.
Uninstall any feature packs
first before you uninstall the application server. If you have a feature pack
installed, uninstalling the WebSphere Application Server product using the
uninstaller program causes the feature pack to fail. However, you should still
uninstall the feature pack after uninstalling the application server to remove
all feature pack product entries and artifacts which might prevent a successful
reinstallation. See Troubleshooting for more information. This same limitation
applies if you are uninstalling a
customized installation package (CIP)
created with the Installation Factory.
Uninstallation
unaugments application server profiles that were previously augmented for
the feature pack, rendering them unusable.
Procedure
- Log on to the system.
Log
on using the same user ID that was used when the product was installed or
as a user that has write permissions to the installation directory. Issue
the ls -al command at the root of the WebSphere Application
Server installation to find the user ID that was used to install the product.
Log on as a user who belongs to the administrators
group or as a user who has write permissions to the installation directory.
- If the feature pack is installed on a Network Deployment product,
then stop the node agent process with the stopNode command.
Stop the node agent process that might be running on the machine.
For example, issue the following command from the
profile_root/bin directory
of a federated node on a Linux workstation to stop the node agent process:
./stopNode.sh
If servers are running and security is enabled, then use
the following command:
./stopNode.sh -user user_ID -password password
- If the feature pack is installed on a Network Deployment product,
then stop the deployment manager dmgr process with the stopManager command.
For example, issue the following command on a Linux workstation from
the
profile_root/bin directory
of the deployment manager profile:
./stopManager.sh -user user_ID -password password
- Stop each running application server with the stopServer command.
Stop all server processes in all profiles on the machine. For example,
issue the following command from the
profile_root/bin directory
to stop the server1 process in the application server profile:
./stopServer.sh server1
If
a server is running and security is enabled, use the following command:
./stopServer.sh server1 -user user_ID -password password
If
you have multiple servers, you can use the
serverStatus command
to find running application servers. Issue the following command from the
profile_root/bin directory
to determine which servers, if any, are running:
./serverStatus.sh -all
- Optional: Back up configuration files, profiles, and
log files to refer to them later if necessary.
Use the backupConfig command
to back up configuration files and profiles.
- Run the uninstall command in the app_server_root/uninstall_websv directory:
uninstall.sh
uninstall.exe
The uninstallation wizard begins and displays the
Welcome panel.
You can also uninstall silently by running the uninstall command
with the following parameters:
Table 1. Silent uninstallation options
Command |
Description |
uninstall -silent |
Use this command to uninstall the feature pack silently
on the base or express editions of WebSphere Application Server. |
uninstall -silent -OPT unaugmentDmgrProfiles="true" |
Use this command to uninstall the feature pack silently
on the Network Deployment edition of WebSphere Application Server. The -OPT
unaugmentDmgrProfiles="true" option is required only if you have
a deployment manager profile augmented with the feature pack. |
- If you are using the wizard, then click Next to
begin uninstalling the product.
The uninstaller wizard displays
a confirmation panel that lists a summary of the components that you are uninstalling.
- Click Next to continue uninstalling the
product.
- Click Finish to close the wizard after
the wizard removes the product.
- Review the uninstallation log files located in the app_server_root/logs/uninstall/webservices directory.
- Delete the application server profiles
that are no longer usable with the manageprofiles command.
Review the list of the invalid profiles that are displayed by the uninstallation
wizard and logged in the uninstallation log file.
- If necessary, delete the remaining /uninstall_websv directory.
Results
This procedure results in uninstalling the feature pack product.
See Installing Feature Pack for Web Services on distributed operating systems if you
want to reinstall the feature pack.
Troubleshooting
Uninstalling
the application server before uninstalling the feature pack might result in
the failure of configuration actions that are responsible for removing Linux
shortcuts. Uninstall any feature pack installations first before uninstalling
the application server to ensure that both products are uninstalled cleanly.
If you have already uninstalled the application server, then run the feature
pack uninstaller to clean up the feature pack installation and to remove any
product registry entries. You can ignore the failed configuration actions
from the application server uninstallation process. However, manually remove
the entire application server directory afterwards.