Uninstalling the product

Uninstall WebSphere Application Server to remove the core product files.

Before you begin

If you have problems uninstalling after upgrading a trial to the full product or upgrading an Express® product to the full base product, you might have used the product disc image to upgrade a trial that was installed from a customized installation package (CIP). You must use a full product CIP to upgrade a trial CIP. Otherwise, you cannot uninstall the trial CIP. Use the manual uninstall procedure in such as case. See Uninstalling manually for more information.

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.

About this task

This procedure uninstalls the WebSphere Application Server product.

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. [AIX] [HP-UX] [Linux] [Solaris] Log on using the same user ID that was used when the product was installed.

    Issue the ls -al command at the root of the WebSphere Application Server installation to find the user ID that was used to install the product.

  2. [Windows] Log on as a user who belongs to the Administrators group or as the user who installed the product.
  3. 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.

  4. Stop each running application server with the stopServer command.
    Stop all server processes in all profiles on the machine. For example, issue the following command from the profile_root/bin directory to stop the server1 process in the application server profile:
    ./stopServer.sh server1
    If a server is running and security is enabled, use the following command:
    ./stopServer.sh server1 -user user_ID -password password
  5. Optional: Back up configuration files and log files to refer to them later if necessary.

    Use the AdminTask command scripting interface to create a configuration archive file of an existing WebSphere Application Server profile, for example.

    The uninstaller program removes all profiles by default, 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, or use the -OPT removeProfilesOnUninstall="false" parameter on the uninstall command.

    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.

  6. Issue the uninstall command.
    Supported configurations [Windows 7] [Fix Pack 29 or later] Supported configurations: On the Microsoft Windows 7 and Windows Server 2008 R2 operating systems, you might encounter the following error message when you launch a graphical user interface to install or uninstall the product:
    The installer is unable to run in graphical mode. Try running the installer with the -console or -silent flag". This issue is specific to using Windows 7 or Windows Server 2008 R2.

    For more information, see the documentation about the problems using the graphical installation process.

    sptcfg
    Run the uninstall command:

    The uninstaller wizard begins and displays the Welcome panel.

    You can also issue the uninstall command with a silent parameter to use the wizard without the graphical user interface.

    Issue the following command to start the uninstaller wizard in silent mode, without the graphical user interface, and to remove all profiles.
    Avoid trouble Avoid trouble: If any of the profiles were migrated to a new version of the product, you must either shut down the new migrated deployment managers before uninstalling the product, or include the removeProfilesOnUninstall="false" parameter on the uninstall command. Either of these options prevents the migrated profiles from being deleted when you uninstall the old version of the product.gotcha
    Issue the following command to start the uninstaller wizard in silent mode and to leave all profiles intact:
    • [AIX] [HP-UX] [Linux] [Solaris] app_server_root/uninstall/uninstall -silent -OPT removeProfilesOnUninstall="false"
    • [Windows] app_server_root\uninstall\uninstall -silent -OPT removeProfilesOnUninstall="false"
  7. 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 components that you are uninstalling.

    1. Click Next to continue uninstalling the product.

      When using the wizard, a panel allows you to choose whether or not the uninstaller deletes all profiles before it deletes the core product files. By default, all profiles will be deleted, but this option can be deselected on the panel.

      To change the default behavior, start the wizard with this command:
      uninstall -OPT removeProfilesOnUninstall="false"

      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.
  8. Review the log file.

    Review the app_server_root/logs/uninstlog.txt file.

    Review the app_server_root/logs/uninstall/log.txt file.

    The log file records file system or other unusual errors. Look for the INSTCONFSUCCESS indicator of success in the log:
    (date_time), 
    Uninstall, com.ibm.ws.install.ni.ismp.actions.
    SetExitCodeAction, msg1, 
    CWUPI0000I: EXITCODE=0
    (date_time), 
    Uninstall, com.ibm.ws.install.ni.ismp.actions.
    ISMPLogSuccessMessageAction, msg1, 
    INSTCONFSUCCESS
  9. If any product files remain, uninstall manually before reinstalling.

    The uninstaller program leaves some log files, including the app_server_root/logs/uninstall/log.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.

Results

This procedure results in uninstalling the WebSphere Application Server product.

What to do next

After uninstalling the product 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.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 4:53:43 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-dist&topic=tins_uninstall
File name: tins_uninstall.html