Managing an Access Manager 7.1 WAR File Deployment

After you deploy an Access Manager WAR file, you might need to perform the following tasks:

• Redeploying an Access Manager Instance

• Removing an Access Manager Instance

• Migrating From File System Configuration to Directory Server Configuration

• Uninstalling Access Manager Using the Java ES Uninstaller

Redeploying an Access Manager Instance

In this scenario, you want to redeploy an Access Manager instance using the web container administration console or CLI commands, without having to reconfigure the Access Manager instance.

Access Manager uses the same datastore (either Directory Server or File System) that was configured to store the configuration data before the redeployment. The location of the configuration directory is not changed.

To Redeploy an Access Manager Instance

1. Undeploy the Access Manager instance.

2. Restart the Access Manager web container.

3. Redeploy the Access Manager instance.

   After a successful redeployment, Access Manager accesses its configuration data either from Directory Server or File System by using the single WAR bootstrap file and then displays the login page.

Removing an Access Manager Instance

In this scenario, you want to completely remove an existing configured Access Manager instance that was deployed from a WAR file.

To Completely Remove an Access Manager Instance

1. Undeploy Access Manager using the web container administration console or CLI command.

2. Manually remove the Access Manager related additions from the server policy file.

3. If you deployed Access Manager on IBM WebSphere Application Server, manually remove the Access Manager related entries from the web container's server.xml configuration file.

4. From the Access Manager single WAR bootstrap file, determine the location of configuration directory for the instance.

   For information about the bootstrap file, see Access Manager 7.1 Single WAR Bootstrap File.

5. Delete the Access Manager configuration directory.

6. Delete the Access Manager instance specific single WAR bootstrap file.

7. Restart the Access Manager web container for these changes to take effect.

Migrating From File System Configuration to Directory Server Configuration

In this scenario, you deployed Access Manager from a WAR file using the File System option to store the configuration data and you want to migrate the data to Directory Server. Command-line utilities are not provided to migrate the configuration data. Directory Server must be installed and running before you perform the following steps.

To Migrate From File System to Directory Server to Store Configuration Data

1. From the Access Manager single WAR bootstrap file, determine the location of configuration directory for the instance.

   For information about the bootstrap file, see Access Manager 7.1 Single WAR Bootstrap File.

2. Delete the configuration directory for the Access Manager instance.

3. Restart the Access Manager web container using the web container administration console or CLI command.

4. Reconfigure Access Manager using the Configurator and specify Directory Server to store the configuration data.

Uninstalling Access Manager Using the Java ES Uninstaller

Consider the following scenario:

1. You installed Access Manager 7.1 by running the Java ES installer with the Configure Later option.

2. You create an Access Manager WAR file by running the amconfig script with DEPLOY_LEVEL=10.

3. You deployed the WAR file into a web container using the container's CLI or Admin console.

4. You now want to uninstall Access Manager using the Java ES uninstaller.

The Java ES uninstaller uses the com.sun.identity.webcontainer property in the AMConfig.properties file to determine the Access Manager web container. For this scenario, this property is always set to WEB_CONTAINER, regardless of the web container where the Access Manager WAR file is actually deployed. During uninstallation, the uninstaller displays the Access Manager panel to gather Web Server information, even though the WAR file might be deployed on Sun Java System Application Server, BEA WebLogic Server, or IBM WebSphere Application Server.

To continue with the uninstallation, accept the default values in Access Manager Web Server uninstaller panel and click Force Uninstallation.