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.
Why and when to perform this task
This procedure uninstalls the WebSphere Application Server Network Deployment product.
Steps for this task
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.
./stopManager.sh -user user_ID -password password
./stopNode.sh
./stopNode.sh -user user_ID -password password
If security is disabled, the uninstaller program can stop all WebSphere Application Server 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.
./stopServer.sh server1
./stopServer.sh server1 -user user_ID -password password
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. You cannot reuse profiles so there is no need to back up an entire profile.
C:\IBM\WebSphere\AppServer\_uninst> uninstall.exe
./uninstall
The uninstaller wizard begins and displays the Welcome panel.
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.
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.
If you must manually clean up the configuration on the managed node, you can attempt the following unsupported procedure:
Go to the install_root/profiles/node_profile_name/config/cells/ directory. Rename the cell_name directory to the original name.
Go to the install_root/profiles/node_profile_name/config/cells/original_cell_name/nodes directory to look for the dmgr_node_name directory that you must delete.
The file is in the install_root/profiles/node_profile_name/bin diorectory. Change the value of the WAS_CELL variable to the original cell name.
Open the administrative console of the deployment manager and click System administration > Nodes > node_name > 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:
Go to the install_root/profiles/dmgr_profile_name/config/cells/cell_name/nodes directory to find the deleted_node_name file.
Go to the install_root/profiles/dmgr_profile_name/config/cells/cell_name/buses directory to find the deleted_node_name file.
Go to the install_root/profiles/dmgr_profile_name/config/cells/cell_name/coregroups/deleted_node_name directory to find the file.
Go to the install_root/profiles/dmgr_profile_name/config/cells/cell_name/coregroups/deleted_node_name 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 you 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.