---
title: Uninstall AM
description: This page describes how to remove AM software.
component: pingam
version: 8.1
page_id: pingam:installation:removing-instances
canonical_url: https://docs.pingidentity.com/pingam/8.1/installation/removing-instances.html
keywords: ["Install"]
page_aliases: ["install-guide:removing-instances.adoc"]
---

# Uninstall AM

This page describes how to remove AM software.

To remove a single server from a multi-server deployment, select Deployment > Servers > *server name* then click [icon: ellipsis-v, set=fas]and [icon: times, set=fas]Delete.

You can find instructions on removing agents in the [Web Agents Installation Guide](https://docs.pingidentity.com/web-agents/2025.3/installation-guide/uninstallation.html) and the [Java Agents Installation Guide](https://docs.pingidentity.com/java-agents/2025.3/installation-guide/uninstallation.html).

After you have deployed and configured AM, you might have as many as four locations where AM files are stored on your system.

The following steps remove the AM software. After removing all the software, remove the AM configuration data.

1. Shut down the web application container where you deployed AM.

   ```bash
   $ /etc/init.d/tomcat stop
   Password:
   Using CATALINA_BASE:   /path/to/tomcat
   Using CATALINA_HOME:   /path/to/tomcat
   Using CATALINA_TMPDIR: /path/to/tomcat/temp
   Using JRE_HOME:        /path/to/jdk/jre
   Using CLASSPATH:       /path/to/tomcat/bin/bootstrap.jar:
    /path/to/tomcat/bin/tomcat-juli.jar
   ```

1) Unconfigure AM by removing the configuration files in the $HOME directory of the user running the web application container.

   For example:

   ```bash
   $ rm -rf $HOME/am $HOME/.openamcfg
   ```

   To uninstall AM and its associated configuration files, delete the following directories:

   * *The configuration directory*.

     If you didn't use the default configuration location (`$HOME/am`), check the value of the `Base installation directory` property under Deployment > Servers > *server name* > General > System.

   * *The hidden directory that holds a file pointing to the configuration directory*.

     For example, if you are using Apache Tomcat as the web container, this file could be `$HOME/.openamcfg/AMConfig_path_to_tomcat_webapps_am_`.

2) Remove the configuration manually from your directory server. The default base DN for AM configuration data is `ou=am-config`.

   |   |                                                                                                                                                                   |
   | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | At this point, you can restart the web container and reconfigure AM if you only want to start over with a clean configuration rather than removing AM completely. |

3) Undeploy the AM web application.

   For example, if you are using Apache Tomcat as the web container, remove the `.war` file and expanded web application from the container:

   ```bash
   $ cd /path/to/tomcat/webapps/
   $ rm -rf am.war am/
   ```