This page shows you how to uninstall AM.
After you have deployed and configured AM, you may have as many as four locations where AM files are stored on your system.
Following the steps below removes the AM software and the internal configuration store. If you used an external configuration store, you can remove AM configuration data after removing all the software.
Shut down the web application container in which you deployed AM.
$ /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
Unconfigure AM by removing the configuration files found in the $HOME directory of the user running the web application container.
A full uninstall of AM and configuration files consists of removing the following directories:
The configuration directory, by default
$HOME/openam. If you did not use the default configuration location, 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
$ rm -rf $HOME/openam $HOME/.openamcfg
Remove the configuration manually from your external directory server. The default base DN for the AM configuration is
At this point, you can restart the web container and configure AM anew if you only want to start over with a clean configuration rather than removing AM completely.
Undeploy the AM web application.
For example, if you are using Apache Tomcat as the web container, remove the
.warfile and expanded web application from the container:
$ cd /path/to/tomcat/webapps/ $ rm -rf openam.war openam/