Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Deploy and administering enterprise applications


Uninstall enterprise application files by dragging them from a monitored directory

After an application file no longer is needed, you can uninstall it by removing its EAR, web application archive (WAR), Java archive (JAR), or SAR from a monitored directory. An enterprise application file must conform to the Java Platform, Enterprise Edition (Java EE) specification.

This topic assumes that you previously installed an enterprise application or module on a server or cluster by dragging or copying it to a monitored directory and that you want to delete it from the server or cluster. The EAR, JAR, WAR, or SAR file exists in a monitored subdirectory:

For base (stand-alone) application servers on distributed operating systems, the monitored directory is under the application server profile. The directory path is WAS_HOME/profiles/application_server_profile_name/monitoredDeployableApps/servers/server_name

For dmgrs on distributed operating systems, the monitored directory is under the dmgr profile:

Restriction: Installing an EAR, JAR, WAR, or SAR file by adding it to a monitored directory is available only on distributed and z/OS operating systems. It is not supported on IBM i operating systems.

For applications previously installed by adding an EAR, JAR, WAR, or SAR file to a monitored monitoredDeployableApps subdirectory, you can uninstall the application or module from the application server by dragging or deleting the EAR, JAR, WAR, or SAR file from the monitoredDeployableApps subdirectory.

The product scans a monitored directory for new applications no more frequently than every five seconds, by default. The server or cluster must be running for the product to notice changes to files in its monitored directory.

After not finding the EAR, JAR, WAR, or SAR file in the monitored directory, the product stops the application or module and uninstalls the file from the application server or cluster. Also, the product removes application files from the directory for installed applications:

Uninstall an application file deletes it from the product configuration repository and deletes the application module binaries from the file system of the node where the application modules are installed.

This topic assumes that you use a graphical file browser to drag or delete the EAR, JAR, WAR, or SAR file from the directory. Alternatively, you can use operating system commands to delete a file from a monitored directory.


Procedure

  1. Ensure that the application server or cluster from which to remove the enterprise application file is running.

    To see which servers or clusters are running, you can use the serverStatus -all command.

    To start a server, you can use the startServer server_name

    command.

    For example, for a stand-alone application server node with a profile name of AppSrv02, run the serverStatus command from a command prompt at the WAS_HOME/profiles/AppSrv02/bin directory: 

    serverStatus -all

    If the server is not running, start the server. For example, to start an application server named server1 on AppSrv02, run the startServer command from a command prompt at the WAS_HOME/profiles/AppSrv02/bin directory: 

    startServer server1
    The Server server1 open for e-business message indicates that the server is running.

  2. Open a file browser and locate the monitored directory.

    For example, for server1 in the AppSrv02 profile, locate the WAS_HOME/profiles/AppSrv02/monitoredDeployableApps/servers/server1 directory.

  3. Remove the EAR, JAR, WAR, or SAR file that you want to uninstall.

    For example, drag or delete the DynaCacheEsi.ear file from the WAS_HOME/profiles/AppSrv02/monitoredDeployableApps/servers/server1 directory.


Results

The product stops the application or module and uninstalls it from the application server or cluster.

For the AppSrv02 example, the product writes messages about the uninstallation to the SystemOut.log file in...

WAS_HOME/logs/server_name

/blockquote> The messages start with the CWLDD message key.

New feature: Beginning in WAS v8.0 you can configure the server to use the HPEL log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.New feature:

For uninstallations from a federated node of a dmgr, if a node agent is stopped, the product uninstalls the application or module at the dmgr level, but does not synchronize the changes with the node. The changes will occur at the node the next time the agent is running and a node synchronization occurs.


What to do next

Examine the server or cluster to verify that the application or module is no longer installed.

If the uninstallation is not successful, read messages in the SystemOut.log and fix the error condition. Add the EAR, JAR, WAR, or SAR file back into the monitored monitoredDeployableApps subdirectory, wait for the product to detect the file, and then remove it from the directory again. If the uninstallation still is not successful, use the admin console or a wsadmin script to uninstall the application file.
Install enterprise application files by adding them to a monitored directory
Uninstall enterprise applications using the console
Uninstall enterprise applications using wsadmin.sh
Deploy and administering enterprise applications
Use HPEL to troubleshoot applications


Related


Directory conventions

+

Search Tips   |   Advanced Search