Uninstall the feature
pack to remove the core product files.
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.
The uninstaller program removes registry entries, uninstalls
the product, and removes all related features. The uninstaller program
does not remove log files in the installation root directory.
newfeatIf you have
a feature pack installed, uninstalling the WebSphere Application Server
product using the Version 6.1.0 uninstaller program causes the feature
pack to stop working because the uninstallation removes the server.
However, you can uninstall the feature pack after uninstalling the
WebSphere Application Server product. This same limitation applies
if you are uninstalling a CIP.
About this task
This procedure uninstalls the feature pack.
Uninstalling
a feature pack changes feature pack profiles. Uninstallation makes
an application server profile that previously was augmented for the
feature pack unusable and no longer valid. Uninstallation unaugments
a deployment manager profile, resulting in deployment manager profile
that is usable and still valid.
The time required
to uninstall is dependent on the processing speed of your machine.
As a rough guideline, uninstalling the core product files and one
application server profile takes approximately 10 minutes when using
the uninstall command.
Procedure
Log on using the same
user ID that was used when the product was installed. 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 the user who installed the product.
- If
the feature pack is installed on a Network Deployment product, 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 machine to stop the node agent process:
./stopNode.sh
If servers are running and security is enabled,
use the following command:
./stopNode.sh -username username -password password
- If
the feature pack is installed on a Network Deployment product, stop
the deployment manager dmgr process with the stopManager command.
Stop all dmgr processes that are running on the machine.
For example, issue this command on a Linux machine from the
profile_root/bin directory
of the deployment manager profile:
./stopManager.sh -username username -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.
- Issue the uninstall command.
Supported configurations: On the Microsoft Windows 7 and Windows Server 2008 R2
operating systems, you might encounter the following error message
when you launch a graphical user interface to install or uninstall
the product:
The installer is unable to run in graphical mode. Try running the installer with the -console or -silent flag". This issue is specific to using Windows 7 or Windows Server 2008 R2.
For
more information, see the documentation about the problems using the
graphical installation process.
sptcfg
The uninstaller wizard begins and displays
the Welcome panel.
You can also issue the uninstall command
with a silent parameter to use the wizard without the graphical user
interface.
Issue
the following command to start the uninstaller wizard in silent mode,
without the graphical user interfaces:
uninstall -silent -OPT unaugmentDmgrProfiles="true"
- If you are using the wizard, 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.
After
uninstalling profiles, the uninstaller program deletes the core product
files in component order.
- Click Finish to close the wizard
after the wizard removes the product.
- If
the uninstallation program did not uninstall the feature pack enablement
extensions, use the Update Installer to uninstall the enablement extensions.
See Uninstalling fix packs, interim features, test fixes, or fix packs delivered as a CIP slip install.
- Review
any log files if necessary.
- If any product files remain, uninstall manually before
reinstalling.
Manually uninstall the product to remove all artifacts
of the product so that you can reinstall into the same installation
root directory. If you do not plan to reinstall, you do not need to
manually uninstall.
If necessary, delete the uninstall_websv directory
for the Web Services feature pack if necessary.
Results
This procedure results in uninstalling the product.
Any application
server profile that previously was enabled with the feature pack is
no longer valid. Any deployment manager profile that previously was
augmented for the feature pack is unaugmented resulting in a deployment
manager profile that is still valid.
What to do next
After uninstalling the product and cleaning the system
with the manual uninstall procedure, you can reinstall.
See Task overview: Installing for an overview of installing the
product and creating a functional e-business environment.