Uninstalling enterprise applications using the wsadmin scripting tool

You can use the AdminApp object or the AdminApplication script library to uninstall applications.

Before you begin

Start the wsadmin scripting tool.

About this task

There are two ways to complete this task. This topic uses the AdminApp object to uninstall enterprise applications. Alternatively, you can use the scripts in the AdminApplication script library to install, uninstall, and administer your application configurations.

The scripting library provides a set of procedures to automate the most common administration functions. You can run each script procedure individually, or combine several procedures to quickly develop new scripts.

Procedure

  1. Uninstall the application:

    Specify the name of the application you want to uninstall, not the name of the enterprise archive (EAR) file.

    • Using Jacl:
      $AdminApp uninstall application1
    • Using Jython:
      AdminApp.uninstall('application1')
    Table 1. uninstall command elements. Run the uninstall command to remove an application from a server.
    Element Description
    $ is a Jacl operator for substituting a variable name with its value
    AdminApp is an object supporting application objects management
    uninstall is an AdminApp command
    application1 is the name of the application to uninstall
  2. Save the configuration changes.
    Use the following command example to save your configuration changes:
    AdminConfig.save()
  3. In a network deployment environment only, synchronize the node.
    Use the syncActiveNodes script from the AdminNodeManagement script library to synchronize each active node in your configuration:
    AdminNodeManagement.syncActiveNodes()

Results

Uninstalling an application removes it from the application server configuration and from each server that the application was installed on. The system deletes the application binaries (EAR file contents) from the installation directory. This occurs when the configuration is saved for single server product versions or when the configuration changes are synchronized from the deployment manager to the individual nodes for network deployment configurations.