Uninstalling Network Deployment

This task describes uninstalling the WebSphere Application Server Network Deployment product.

Before you begin

The uninstaller program removes registry entries, uninstalls the product, and removes all related features. The uninstaller program does not remove log files in the installation root directory.

The uninstaller program removes all profiles, including all of the configuration data and applications in each profile. Before you start the uninstall procedure, back up the config folder, the installableApps folder, and the installedApps folder of each profile, if necessary. See Using command line tools for a description of managing configuration files. Back up all applications that are not stored in another location.

Overview

See the following topics to uninstall other components on the product disc:

Procedure

Log on as root on a Linux or UNIX system, or as a user who belongs to the administrator group on a Windows system.
Run the uninstaller program for the Web server plug-ins for WebSphere Application Server.
If a Web server is configured to run with the Application Server, uninstall the plug-ins to remove the configuration from the Web server. See Uninstalling the Web server plug-ins for WebSphere Application Server.
Stop the deployment manager dmgr process with the stopManager command.
Stop all dmgr processes that are running on the machine. For example, issue this command on a Linux machine from the /opt/IBM/WebSphere/AppServer/profiles/dmgr_profile/bin directory
```
./stopManager.sh -user user_ID -password password
```
Stop the nodeagent process with the stopNode command.
Stop the nodeagent process that might be running on the machine. For example, issue the following command from the /opt/IBM/WebSphere/AppServer/profiles/app_server_profile/bin directory of a federated node on a Linux machine to stop the nodeagent process
```
./stopNode.sh 
```
If servers are running and security is enabled, use the following command
```
./stopNode.sh -user user_ID -password password
```
Stop each running Application Server with the stopServer command.
If security is disabled, the uninstaller program can stop all WAS processes automatically. If servers are running and security is enabled, the uninstaller program cannot shut down the servers and the uninstall procedure fails. Manually stop all servers before uninstalling.
Stop all server processes in all profiles on the machine. For example, issue the following command from the /opt/IBM/WebSphere/AppServer/profiles/app_server_profile/bin directory on a Linux machine to stop the server1 process in the profile
```
./stopServer.sh server1
```
If servers are running and security is enabled, use the following commands
```
./stopServer.sh server1 -user user_ID -password password
```
Optional: Back up configuration files and log files to refer to them later, if necessary.
The uninstaller program does not remove log files in the installation root directory. The uninstaller program removes 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 it later, if necessary. We cannot reuse profiles so there is no need to back up an entire profile.
Issue the uninstall command. The command file is named:
- uninstall
- uninstall.exe
Issue the uninstall command:
- install_root/_uninst/uninstall
- install_root\_uninst\uninstall.exe
Call the program directly from the install_root \_uninst directory. For example, if the installation root is C:\IBM\WebSphere\AppServer, issue the following command
```
C:\IBM\WebSphere\AppServer\_uninst> uninstall.exe
```
Issue the uninstall command from the install_root/_uninst directory
```
./uninstall
```
The uninstaller wizard begins and displays the Welcome panel.
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.
Click Next to continue uninstalling the product.
The uninstaller deletes all profiles before it deletes the core product files. Before using the uninstaller, back up any profile data that you intend to preserve. The uninstaller does not retain data files or configuration data that is in the profiles.
After uninstalling profiles, the uninstaller program deletes the core product files in component order.
Click Finish to close the wizard after the wizard removes the product.
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, 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 save. With a valid backup of the configuration, one can always use the restoreConfig command to get back to a previously existing state in the configuration.
We can also use the following command to remove the node when the deployment manager is not running. Issue the command from the install_root/profiles/managed_node_profile/bin directory on the machine with the managed node:
- removeNode.sh -force
- removeNode.bat -force
If manually clean up the configuration on the managed node, one can attempt the following unsupported procedure:
1. Rename the cell directory for the node to the original name if the current name is not the original name.
  Go to the install_root/profiles/node_profile/config/cells/ directory. Rename the cell directory to the original name.
2. Delete the dmgr_node directory if it exists.
  Go to the install_root/profiles/node_profile/config/cells/original_cell/nodes directory to look for the dmgr_node directory that 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 install_root/profiles/node_profile/bin diorectory. 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 > node > Remove node.
If the administrative console cannot successfully remove the node, run the following command with the deployment manager running:
- install_root/bin/cleanupNode.sh node
- install_root/bin/cleanupNode.bat 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 save. With a valid backup of the configuration, one can always use the restoreConfig command to get back to a previously existing state in the configuration.
If manually clean up the configuration, one 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 install_root/profiles/dmgr_profile/config/cells/cell/nodes directory to find the deleted_node file.
2. Within the buses directory of the deployment manager, remove the configuration directory for the node that you deleted.
  Go to the install_root/profiles/dmgr_profile/config/cells/cell/buses directory to find the deleted_node 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 install_root/profiles/dmgr_profile/config/cells/cell/coregroups/deleted_node 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 install_root/profiles/dmgr_profile/config/cells/cell/coregroups/deleted_node directory to find the file.

Result

This procedure uninstalls the Network Deployment product.

After running the uninstall command, the directory structure has only a few remaining directories. The logs directory is one of the few directories with files.

What to do next

The uninstaller program leaves some log files, including the install_root/logs/uninstlog.txt file.

Manually uninstall the product to remove all artifacts of the product so that one can reinstall into the same installation root directory. If you do not plan to reinstall, you do not need to manually uninstall.

See Uninstalling manually for more information.