Use this procedure to silently uninstall IBM WebSphere ESB and
the underlying copy of WebSphere Application Server Network
Deployment.
Before you begin
Before uninstalling
WebSphere ESB using
this procedure, do the following:
- Ensure that you have an existing WebSphere ESB installation
that you now want to uninstall.
- Determine that you want to uninstall WebSphere ESBsilently,
instead of using the Uninstallation graphical user interface (GUI).
- Determine if you want to uninstall the underlying WebSphere Application Server Network
Deployment product when you are uninstalling WebSphere ESB.
- If you elect to uninstall the underlying 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 Network
Deployment product, any WebSphere ESB profiles
that have been created or augmented will be unaugmented back to WebSphere Application Server Network
Deployment profiles if no other product has augmented the profiles after WebSphere ESB.
- 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.
- 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 the
database are found in the tcei_install_removeConfig.dita.
- Ensure that 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.
Why and when to perform this task
To uninstall WebSphere ESB silently,
do the following:
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 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 ServerNetwork
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 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 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
- Optional: 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 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.
- Run the command that uninstalls WebSphere ESB silently.
On Linux and UNIX platforms: install_root/_uninstwbi/uninstall -silent
[-W uninstallWelcomePanel_UninstallWizardBean.uninstallUnderlyingWAS \
="true"]
On Windows platforms: install_root\_uninstwbi\uninstall.exe -silent
[-W uninstallWelcomePanel_UninstallWizardBean.uninstallUnderlyingWAS \
="true"]
where the –W uninstallWelcomePanel_UninstallWizardBean.uninstallUnderlyingWAS
=“true” option can be used to uninstall the underlying WebSphere Application Server Network
Deployment installation. Do not include this option if you want WebSphere Application Server Network
Deployment to remain installed.
- 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 ESB,
and if selected, WebSphere Application Server Network
Deployment. After running the silent uninstallation, 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: To prevent installation problems, you should uninstall both WebSphere ESB and
the underlying WebSphere Application Server Network
Deployment product if you plan to reinstall WebSphere ESB 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.