WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Uninstalling the product using the GUI

Use this procedure to uninstall IBM WebSphere ESB and the underlying copy of WebSphere Application Server Network Deployment with the Uninstallation wizard graphical user interface (GUI).

Before you begin

Before uninstalling WebSphere ESB using this procedure, ensure that:
  • You want to uninstall WebSphere ESB interactively.
  • You know 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.
  • 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. For information about removing these applications and database, see Removing the Common Event Infrastructure configuration
  • 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: For Windows platforms 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 ESB, WebSphere Application Server Network Deployment, and one profile takes approximately 20 minutes.

To uninstall WebSphere ESB, perform the following steps.

Steps for this task

  1. 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.
  2. 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.

  3. 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):
    • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/bin/stopManager.sh -user user_ID -password password
    • For Windows platforms On Windows platforms: profile_root\bin\stopManager.bat -user user_ID -password password
  4. 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):
    • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/bin/stopNode.sh
    • For Windows platforms On Windows platforms: profile_root\bin\stopNode.bat
    If servers are running and security is enabled, use one of the following commands instead:
    • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/bin/stopNode.sh -user user_ID -password password
    • For Windows platforms On Windows platforms: profile_root\bin\stopNode.bat -user user_ID -password password
  5. 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:
    • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/bin/stopServer.sh server1
    • For Windows platforms On Windows platforms: profile_root\bin\stopServer.bat server1
    If servers are running and security is enabled, use one of the following commands instead:
    • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/bin/stopServer.sh server1 -user user_ID -password password
    • For Windows platforms On Windows platforms: profile_root\bin\stopServer.bat server1 -user user_ID -password password
  6. 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.

  7. Issue the uninstall command from a command line.
    Issue one of the following commands, depending on platform:
    • LINUX platforms UNIX platforms On Linux and UNIX platforms: install_root/_uninstwbi/uninstall
    • For Windows platforms On Windows platforms: install_root\_uninstwbi\uninstall.exe
    The Uninstallation wizard starts and the Welcome panel is displayed.
  8. In the Welcome panel, select whether to uninstall the underlying WebSphere Application Server Network Deployment product when uninstalling WebSphere ESB. Then click Next. 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, and you did not elect to uninstall the underlying 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, and you did not elect to uninstall the underlying 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 ESB profiles will be unusable. Proceed to step 9.
    • If no servers are running and you did elect to uninstall the underlying WebSphere Application Server Network Deployment product, a Warning panel is displayed, which alerts you that your WebSphere ESB profiles will be deleted. Proceed to step 9.
  9. From the Warning panel, select whether to continue with the uninstallation. Click Next to continue with the uninstallation or Back if you want to reconsider uninstalling the product. This example procedure assumes you want to continue with the uninstallation. The Uninstallation Summary panel is displayed.
  10. Review the summary of the product and features that you are uninstalling.

    Click 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 Network Deployment product, the uninstaller performs the following tasks in the following order:
    • Unaugments profiles that were last augmented by WebSphere ESB.
    • Uninstalls WebSphere ESB.
    • Uninstalls WebSphere Application Server Network Deployment, which deletes the profiles.
    The Uninstallation Complete panel is displayed.
  11. Click Finish to close the Uninstallation wizard.
  12. 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:
    • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/bin removeNode.sh -force
    • For Windows platforms 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:

    1. 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:
      • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/config/cells/
      • For Windows platforms On Windows platforms: profile_root\config\cells\
    2. 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:
      • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/config/cells/original_cell_name/nodes
      • For Windows platforms On Windows platforms: profile_root\config\cells\original_cell_name\nodes
    3. 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:
      • LINUX platforms For Windows platforms On Linux and UNIX platforms: profile_root/bin
      • For Windows platforms On Windows platforms: profile_root\bin
      Change the value of the WAS_CELL variable to the original cell name.
  13. 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.

    If the administrative console cannot successfully remove the node, run the following command with the deployment manager running:
    • LINUX platforms UNIX platforms On Linux and UNIX platforms: install_root/bin/cleanupNode.shnode_name
    • For Windows platforms On Windows platforms: install_root\bin\cleanupNode.batnode_name

    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:

    1. 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:
      • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/config/cells/cell_name/nodes
      • For Windows platforms On Windows platforms: profile_root\config\cells\cell_name\nodes
    2. 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:
      • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/config/cells/cell_name/buses
      • For Windows platforms On Windows platforms: profile_root\config\cells\cell_name\buses
    3. 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:
      • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/config/cells/cell_name/coregroups/deleted_node_name
      • For Windows platforms On Windows platforms: profile_root\config\cells\cell_name\coregroups\deleted_node_name
    4. 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:
      • LINUX platforms UNIX platforms On Linux and UNIX platforms: profile_root/config/cells/cell_name/coregroups/deleted_node_name
      • For Windows platforms 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 Uninstallation wizard, the directory structure has only a few remaining directories, including the logs directory.

The uninstallation program leaves some log files in this directory, including the following:
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:

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.


Task topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\doc\tins_gui_uninstall.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)