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.
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_web2fep 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. |
- 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/web2fep directory.
- If necessary, delete the remaining /uninstall_web2fep directory.
Results
This procedure results in uninstalling the feature pack
product.
See Installing Feature Pack for Web 2.0 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.
Manual Uninstallation
If you have encountered an error during installation
or uninstallation, then follow these instructions to manually remove
the feature pack.
- Delete the following directories:
- Delete the app_server_root/properties/WEB2FEPCustomConstants.properties file.
- Delete the following files from app_server_root/properties/version:
- ajax.client.runtime.component
- ajax.proxy.component
- dev.guide.component
- eclipse.site.component
- feedsphere.component
- legal.web2fep.component
- lib.jaxrs.61.component
- lib.json4j.component
- lib.pubsub.61.component
- productspecificfiles.web2fep.component
- rpc.adapter.component
- samples.ajaxhello.component
- samples.feedsphere.component
- samples.jaxrs.61.component
- samples.pbw.61.component
- samples.quotestreamer.component
- samples.rpc.component
- samples.soap.component
- web2fep.doc.index.component
- WEB2FEP.product
- Delete the following files from the app_server_root/properties/version/nif/backup directory:
- fep.web2fep.primary.pak
- fep.web2fep.common.pak
- fep.web2fep.61.pak
- Remove the following directories from app_server_root/properties/version/nif/backup:
- ajax.client.runtime
- ajax.proxy
- dev.guide
- eclipse.site
- feedsphere
- legal.web2fep
- lib.jaxrs.61
- lib.json4j
- lib.pubsub.61
- nif.componentmap.web2fep.61
- nif.componentmap.web2fep.common
- nif.componentmap.web2fep.primary
- productspecificfiles.web2fep
- rpc.adapter
- samples.ajaxhello
- samples.feedsphere
- samples.jaxrs.61
- samples.pbw.61
- samples.quotestreamer
- samples.rpc
- samples.soap
- web2fep.doc.index
- Delete the following files from app_server_root/properties/version/nif/componentmaps:
- componentmap.web2fep.61.xml
- componentmap.web2fep.common.xml
- componentmap.web2fep.primary.xml
- Remove the WEB2FEP entries from the product registry
with the installRegistryUtils command in the app_server_root/bin directory:
- For a root user or adminstrator:
./installRegistryUtils.bat|sh -cleanProduct
-offering WEB2FEP
-installLocation app_server_root
- For a non-root or non administrator user, where user_home is
the home directory of the current user:
./installRegistryUtils.bat|sh -cleanProduct
-offering WEB2FEP
-installLocation app_server_root
-userHome user_home