Access Management 7.2.2

Uninstall AM

This topic describes how to remove AM software.

To remove a single server from a multi-server deployment, select Deployment > Servers > Server Name then click and Delete.

You can find instructions on removing agents in the Web Agents Installation Guide and the Java Agents Installation Guide.

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

In a test deployment, the following steps remove the AM software and the internal configuration store. If you used an external configuration store, remove AM configuration data after removing all the software.

  1. 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
  2. Unconfigure AM by removing the configuration files in the $HOME directory of the user running the web application container.

    For example:

    $ rm -rf $HOME/openam $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/openam), 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_openam_.

  3. Remove the configuration manually from your external directory server. The default base DN for the AM configuration is dc=openam,dc=forgerock,dc=org.

    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.
  4. 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:

    $ cd /path/to/tomcat/webapps/
    $ rm -rf openam.war openam/