WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Uninstalling the product

Uninstall WebSphere Application Server Network Deployment 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.

Why and when to perform this task

This procedure uninstalls the WebSphere Application Server Network Deployment product only.

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 the core product files and one application server profile takes approximately 10 minutes when using the uninstall command.

Steps for this task

  1. Issue the uninstall command.
    Issue the uninstall command:

    The uninstaller wizard begins and displays the Welcome panel.

    The next few steps in this procedure describe using the wizard interactively. You can also issue the uninstall command with a silent parameter to use the wizard without the graphical user interface.

    uninstall -silent
  2. 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 product and features that you are uninstalling.

    1. Click Next to continue uninstalling the product.

      The uninstaller deletes all profiles by default before it deletes the core product files.

      The uninstaller retains all profiles by default before it deletes the core product files.

      After uninstalling profiles, the uninstaller program deletes the core product files in component order.

    2. Click Finish to close the wizard after the wizard removes the product.
  3. 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 or federated application server profiles. If you delete a Network Deployment installation where you created an application server profile or 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 the following command to remove the node when the deployment manager is not running. Issue the command from the app_server_root/profiles/managed_node_profile/bin directory on the machine with the managed node:
    • [Linux][UNIX]removeNode.sh -force
    • [Windows]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 the profile_root/config/cells/ directory. Rename the cell_name directory to the original name.

    2. Delete the dmgr_node_name directory if it exists.

      Go to the profile_root/config/cells/original_cell_name/nodes directory to look for the dmgr_node_name directory that you must delete.

    3. Edit the setupCmdLine.sh file on a Linux or UNIX operating system, or the setupCmdLine.sh file on a Windows system and change the cell name to the original cell name.

      The file is in the profile_root/bin directory. Change the value of the WAS_CELL variable to the original cell name.

  4. 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 > node_name > Remove node.

    If the administrative console cannot successfully remove the node, run the following command with the deployment manager running:

    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 the profile_root/config/cells/cell_name/nodes directory to find the deleted_node_name file.

    2. Within the buses directory of the deployment manager, remove the configuration directory for the node that you deleted.

      Go to the profile_root/config/cells/cell_name/buses directory to find the deleted_node_name file.

    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 the profile_root/config/cells/cell_name/coregroups/deleted_node_name directory to find the file.

    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 the profile_root/config/cells/cell_name /coregroups/deleted_node_name directory to find the file.

  5. Uninstall manually before reinstalling.

Result

This procedure results in uninstalling the WebSphere Application Server Network Deployment product.

What to do next

After uninstalling WebSphere Application Server Network Deployment 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.




Sub-topics
uninstall command
vpd.properties file
Uninstalling manually

Related information
Administrative command invocation syntax
Commands for the AdminTask object
Task overview: Installing

Task topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_uninstall.html

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