Uninstalling the product

This task describes how to uninstall WAS Network Deployment.

 

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.

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

This procedure uninstalls the WAS product.

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

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.

 

Procedure

  1. Log on as root on a Linux or UNIX system, or as a user who belongs to the administrator group on a Windows system.

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

  3. 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
    
    

  4. 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
    
    

  5. 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
    

  6. 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.

  7. Uninstall the product.

    Uninstalling Network Deployment

    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.

  8. Review the install_root/logs/uninstlog.txt file.

    The install_root/logs/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
    
    

  9. Uninstall manually before reinstalling.

    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.

 

Result

This procedure results in uninstalling the product.

 

What to do next

After uninstalling the product and cleaning the system with the manual uninstall procedure, one can reinstall.

See Task overview: Installing for an overview of installing the product and creating a functional e-business environment.

 

See also


uninstall command
vpd.properties file
Uninstalling Network Deployment
Uninstalling manually