You can uninstall an instance of Access Manager that was installed by running the amconfig script. You can also temporarily unconfigure an instance of Access Manager, and unless you remove the web container instance, it is still available for you to re-deploy another Access Manager instance later.
The following steps apply to Solaris, HP-UX, and Linux systems.
Log in as an administrator, depending on the web container for the instance.
For example, if Web Server 7 is the web container, log in either as superuser (root) or as the user account for Web Server Administration Server.
Copy the silent configuration input file you used to deploy the instance to a writable directory and make that directory your current directory.
For example, to unconfigure an instance for Web Server 7, the following steps use an input file named amnewinstanceforWS7 in the /unconfigure directory.
In the amnewinstanceforWS7 file, set the DEPLOY_LEVEL variable to one of the values described for an Deployment Mode Variable operation.
For example, set DEPLOY_LEVEL=11 to uninstall (or unconfigure) a full installation.
Run the amconfig script, specifying your edited input file.
For example, on Solaris systems with Access Manager installed in the default directory:
# cd opt/SUNWam/bin/ # ./amconfig -s ./unconfigure/aminstanceforWS61
The -s option runs the script in silent mode. The amconfig script reads the amnewinstanceforWS7 file and then uninstalls the instance.
The web container instance is still available if you want to use it to re-deploy another Access Manager instance later.