Use this procedure to uninstall WebSphere Process Server and the
underlying copy of WebSphere Application Server or WebSphere Application Server
Network Deployment with the Uninstallation Wizard graphical user
interface (GUI).
Before you begin
Before uninstalling WebSphere Process Server using this procedure,
ensure that:
- You want to uninstall WebSphere Process Server interactively.
- You know if you want to uninstall the underlying WebSphere Application
Server or WebSphere Application Server Network Deployment product when you
are uninstalling WebSphere Process Server.
- If you elect to uninstall the underlying WebSphere Application Server
or WebSphere Application Server Network Deployment product, the uninstaller
program also removes all profiles, including all of the configuration data
and applications in each profile.
- If you elect not to uninstall the underlying WebSphere Application Server
or WebSphere Application Server Network Deployment product, any WebSphere
Process Server profiles that have been created or augmented will be unaugmented
back to WebSphere Application Server or WebSphere Application Server Network
Deployment profiles if no other product has augmented the profiles after WebSphere
Process Server.
- You back up the config folder, the installableApps folder,
and the installedApps folder of each profile, if necessary. Back
up all applications that are not stored in another location.
- You remove the event messaging enterprise application, the event database,
and the configuration for the Common Event Infrastructure application, in
that order. The instructions for removing these applications and database
are found in the WebSphere Process Server information center in the
following locations:
- The instructions for removing the event messaging enterprise application
are found in the section Installing > Uninstalling the product > Removing
the Common Event Infrastructure configuration > Removing the event messaging
enterprise application.
- Those for removing the event database, in the section Installing >
Uninstalling the product > Removing the Common Event Infrastructure configuration
> Removing the event database.
- And those for removing the configuration for the Common Event Infrastructure
application, in the section Installing > Uninstalling the product > Removing
the Common Event Infrastructure configuration > Removing the Common Event
Infrastructure application.
- If you configured business process containers, you delete all external
resources manually after uninstalling WebSphere Process Server. To prepare
for this, for each application server where you configured a business process
container, perform the following steps before you uninstall the product:
- If you use WebSphere MQ as the Java Message Service (JMS) provider, use
the administrative console to view the queue connection factory for the business
process container, and make a note of the name of the queue manager so that
you can delete it later.
- If you do not use a Cloudscape database for the business process container,
use the administrative console to view the data source for the business process
container, and make a note of the name of the database so that you can delete
it later. (If you use a Cloudscape database for the business process container,
the database will be deleted automatically.)
- You are uninstalling the product as the root user on a Linux or UNIX system,
or as a member of the Administrator group on a Windows system.
Restriction: The Uninstallation Wizard does not perform partial,
custom, or incremental uninstallations.
Restriction:
On Windows platforms: Windows platforms have a
maximum length for file paths of 256 characters. If a file path for a profile
directory is too long, the Uninstallation Wizard cannot remove the directory.
The file path can be too long because of a long
profile_root directory
name, a long cell name, long process server names, or other long names used
as file folder names in directories within the profile. Although Windows platforms
allow the creation of long file paths, the operating systems do not allow
deletion of the long file paths, even when attempting a manual deletion. To
enable uninstallation if you encounter this problem, rename the directories
and subdirectories for the files left behind to names that have fewer characters.
Then manually delete the directories.
Why and when to perform this task
The uninstallation program is created during product installation.
It is customized for each product installation, with specific disk locations
and routines for removing installed features.
Estimating the time
required to uninstall: The time required to uninstall is dependent on
the processing speed of your machine. As a rough guideline, uninstalling WebSphere
Process Server, WebSphere Application Server Network Deployment, and one process
server profile takes approximately 20 minutes.
To uninstall WebSphere
Process Server, perform the following steps.
Steps for this task
- Log on as the root user on a Linux or UNIX system, or as a user
who belongs to the Administrator group on a Windows system.
- If you are uninstalling the underlying WebSphere Application Server
or WebSphere Application Server Network Deployment product, run the uninstallation
program for the Web server plug-ins for WebSphere Application Server.
If your system includes a Web server configured to run with the WebSphere
Application Server or WebSphere Application Server Network Deployment, uninstall
the plug-ins to remove the configuration from the Web server. See the uninstallation
procedure for this product on the WebSphere Application Server Network Deployment,
version 6.0, information center at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.
- If you have a deployment manager installed, stop the deployment
manager dmgr process with the stopManager command.
Stop
all
dmgr processes that are running on the machine. For example, issue
one of the following commands, depending on platform (where
profile_root represents
the installation directory of the deployment manager profile):

On Linux and UNIX platforms: profile_root/bin/stopManager.sh
-user user_ID -password password
On Windows platforms: profile_root\bin\stopManager.bat
-user user_ID -password password
- Stop the nodeagent process with the stopNode command.
If you have nodes federated to a deployment manager on your system,
stop the nodeagent process that might be running on each machine with a federated
node. For example, issue one of the following commands to stop the nodeagent
process, depending on platform (where
profile_root represents the installation
directory of the federated node):

On Linux and UNIX platforms: profile_root/bin/stopNode.sh
On Windows platforms: profile_root\bin\stopNode.bat
- Stop each running process server with the stopServer command.
Stop all server processes in all profiles on the machine. For example,
issue one of the following commands to stop the server
server1 in
the profile, depending on platform. In this example,
profile_root represents
the installation location of the profile:

On Linux and UNIX platforms: profile_root/bin/stopServer.sh
server1
On Windows platforms: profile_root\bin\stopServer.bat
server1
- Back up configuration files and log files
to refer to them later, if necessary.
The uninstallation program
does not remove log files in the install_root directory. If you elect
to uninstall the underlying WebSphere Application Server or WebSphere Application
Server Network Deployment product, it does remove all profiles and all of
the data in all profiles.
Back up the config folder and the logs folder
of each profile to refer to later, if necessary. You cannot reuse profiles
so there is no need to back up an entire profile.
- Issue the uninstall command from a command line.
The Uninstallation Wizard starts and the Welcome panel is displayed.
- In the Welcome panel, select whether to uninstall the underlying
WebSphere Application Server or WebSphere Application Server Network Deployment
product when uninstalling WebSphere Process Server.
- To uninstall the underlying WebSphere Application Server or WebSphere
Application Server Network Deployment product when uninstalling WebSphere
Process Server, select the Uninstall the underlying WebSphere Application
Server, version 6.0 check box (if WebSphere Application Server is installed)
or select the Uninstall the underlying WebSphere Application Server Network
Deployment, version 6.0 check box (if WebSphere Application Server Network
Deployment is installed). Then select Next to continue.
- To not uninstall WebSphere Application Server or WebSphere Application
Server Network Deployment, leave this check box clear.
One of four panels is displayed:
- If any servers are running on your system, a warning panel alerts you
to shut them down and restart the uninstallation. Cancel the uninstallation
and stop the running servers.
- If no servers are running, if you did not elect to uninstall the
underlying WebSphere Application Server or WebSphere Application Server Network
Deployment product, and the uninstaller determines that profiles can be
unaugmented successfully to WebSphere Application Server profiles, the Uninstallation
summary panel is displayed. Proceed to step 10.
- If no servers are running, if you did not elect to uninstall the
underlying WebSphere Application Server or WebSphere Application Server Network
Deployment product, and the uninstaller determines that profiles cannot be
unaugmented successfully, a warning panel is displayed, which alerts you that
your WebSphere Process Server profiles will be unusable. Proceed to step 9.
- If no servers are running and you did elect to uninstall the underlying
WebSphere Application Server or WebSphere Application Server Network Deployment
product, a warning panel is displayed, which alerts you that your WebSphere
Process Server profiles will be deleted. Proceed to step 9.
- In the warning panel, select whether
to continue with the uninstallation.
- If you elect to uninstall the underlying WebSphere Application Server
or WebSphere Application Server Network Deployment product, the uninstaller
program also removes all profiles, including all of the configuration data
and applications in each profile.
- If you do not elect to uninstall the underlying WebSphere Application
Server or WebSphere Application Server Network Deployment product, any WebSphere
Process Server profiles that have been created or augmented will be unaugmented
back to WebSphere Application Server or WebSphere Application Server Network
Deployment profiles only if no other product has augmented the profiles after
WebSphere Process Server.
If you did not elect to uninstall the underlying WebSphere Application
Server or WebSphere Application Server Network Deployment product and a warning
panel appeared, it means the profiles cannot be unaugmented and will be unusable.
Select
Next to continue with the uninstallation or select
Back if
you want to reconsider uninstalling the product. This example procedure assumes
you want to continue with the uninstallation.
- In the Uninstallation summary panel,
review the summary of the product and features that you are uninstalling.
Select Next to continue uninstalling the product or select Back if
you want to reconsider uninstalling the product. This example procedure assumes
you want to continue with the uninstallation.
Product uninstallation
begins. If you selected to uninstall the underlying WebSphere Application
Server or WebSphere Application Server Network Deployment product, the uninstaller
performs the following tasks in the following order:
- Unaugments profiles that were last augmented by WebSphere Process Server.
- Uninstalls WebSphere Process Server.
- Uninstalls WebSphere Application Server or WebSphere Application Server
Network Deployment, which deletes the profiles.
- In the Uninstallation complete panel, select Finish to close
the Uninstallation Wizard.
- If you configured business process containers, you must delete
all external resources manually.
Do the following:
- If you use WebSphere MQ as the Java Message Service (JMS) provider for
any business process containers, delete the queue managers that you noted
earlier.
- Delete the databases that you noted earlier for each business process
container that does not use a Cloudscape database. (If you use a Cloudscape
database for a business process container, the database was deleted automatically.)
- Remove any configuration entries in the managed node that describe
a deleted deployment manager.
A common topology is to install
the core product files on multiple machines. One machine has the deployment
manager and other machines have managed nodes created from custom profiles.
If you delete an installation where you created a custom profile and federated
the node into a deployment manager cell in another installation, you must
remove the configuration from the deployment manager.
The official
statement of support for a node configuration problem in the managed node
is that you use the backupConfig command after the initial installation.
Use the command again whenever you make significant changes to the configuration
that you must save. With a valid backup of the configuration, you can always
use the restoreConfig command to get back to a previously existing
state in the configuration.
You can also use one of the following commands
on the machine with the managed node to remove the node when the deployment
manager is not running. In this example,
profile_root represents the
installation directory of the managed node profile:

On Linux and UNIX platforms: profile_root/bin
removeNode.sh -force
On Windows platforms: profile_root\bin
removeNode.bat -force
If you must manually clean up the configuration on the managed
node, you can attempt the following unsupported procedure:
- Rename the cell_name directory for the node to the original
name if the current name is not the original name.
Go to one
of the following directories and rename the
cell_name directory to
the original name. In this example,
profile_root represents the installation
directory of the node profile:

On Linux and UNIX platforms: profile_root/config/cells/
On Windows platforms: profile_root\config\cells\
- Delete the dmgr_node_name directory if it exists.
Go to one of the following directories to look for the
dmgr_node_name directory
that you must delete. In this example,
profile_root represents the
installation directory of the node profile:

On Linux and UNIX platforms: profile_root/config/cells/original_cell_name/nodes
On Windows platforms: profile_root\config\cells\original_cell_name\nodes
- Edit the setupCmdLine.sh file on a Linux or UNIX operating
system, or the setupCmdLine.bat file on a Windows system and change
the cell name to the original cell name.
The file is in one
of the following directories, depending on platform. In this example,
profile_root represents
the installation directory of the node profile:

On Linux and UNIX platforms: profile_root/bin
On Windows platforms: profile_root\bin
Change the value of the
WAS_CELL variable to the original cell
name.
- Remove any configuration entries in the deployment manager that
describe a deleted managed node.
Open the administrative console
of the deployment manager and click System administration > Nodes.
Select the check box beside the node you wish to delete and then select Remove
node.
The official statement of support for a node configuration problem
in the deployment manager is that you use the backupConfig command
after the initial installation. Use the command again whenever you make significant
changes to the configuration that you must save. With a valid backup of the
configuration, you can always use the restoreConfig command to get
back to a previously existing state in the configuration.
If you must
manually clean up the configuration, you can attempt the following unsupported
procedure:
- Within the nodes directory of the deployment manager,
remove the configuration directory for the node that you deleted.
Go
to one of the following directories to find the
deleted_node_name file.
In this example,
profile_root represents the installation directory
of the deployment manager profile:

On Linux and UNIX platforms: profile_root/config/cells/cell_name/nodes
On Windows platforms: profile_root\config\cells\cell_name\nodes
- Within the buses directory of the deployment manager,
remove the configuration directory for the node that you deleted.
Go
to one of the following directories to find the
deleted_node_name file.
In this example,
profile_root represents the installation directory
of the deployment manager profile:

On Linux and UNIX platforms: profile_root/config/cells/cell_name/buses
On Windows platforms: profile_root\config\cells\cell_name\buses
- Edit the coregroup.xml file in each subdirectory of
the coregroups directory of the deployment manager. Look for elements
of type coreGroupServers. Remove any coreGroupServers elements that
have a reference to the node that you deleted.
Go to one of
the following directories to find the file. In this example,
profile_root represents
the installation directory of the deployment manager profile:

On Linux and UNIX platforms: profile_root/config/cells/cell_name/coregroups/deleted_node_name
On Windows platforms: profile_root\config\cells\cell_name\coregroups\deleted_node_name
- Edit the nodegroup.xml file in each subdirectory of
the nodegroups directory of the deployment manager. Look for elements
of type members. Remove any members elements that have a reference
to the node that you deleted.
Go to one of the following directories
to find the file. In this example,
profile_root represents the installation
directory of the deployment manager profile:

On Linux and UNIX platforms: profile_root/config/cells/cell_name/coregroups/deleted_node_name
On Windows platforms: profile_root\config\cells\cell_name\coregroups\deleted_node_name
Result
This procedure uninstalls WebSphere Process Server, and if selected,
WebSphere Application Server or WebSphere Application Server Network Deployment.
After running the Uninstallation Wizard, the directory structure has only
a few remaining directories, including the logs directory.
The
uninstlog.txt file records file system
or other unusual errors. Look for the INSTCONFSUCCESS indicator of success
in the log:
Uninstall, com.ibm.ws.install.ni.ismp.actions.
ISMPLogSuccessMessageAction, msg1,
INSTCONFSUCCESS
What to do next
If you intend to reinstall the product into the same installation
root directory, you must do one of the following, depending on the success
of the uninstallation:
- If uninstallation was successful, you must manually remove the install_root directory.
Important: IBM recommends that you uninstall both WebSphere Process
Server and the underlying WebSphere Application Server or WebSphere Application
Server Network Deployment product if you uninstall and plan to reinstall WebSphere
Process Server into the same directory. Therefore the install_root directory,
which you must manually remove, should be empty.
- If uninstallation was not successful, you must manually uninstall the
remaining artifacts of the product. See Preparing for reinstallation after a failed uninstallation for
more information. If you do not plan to reinstall, you do not need to perform
this task.
For more information on the commands mentioned in this topic,
see the WebSphere Application Server Network Deployment, version 6.0, information
center at http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp.