test

Sun Java System Access Manager 7.1 Postinstallation Guide

Access Manager Deployment Scenarios

After you have installed the first instance of Access Manager using the Java Enterprise System installer, you can deploy and configure additional Access Manager instances by editing the configuration variables in the silent configuration input file and then running the amconfig script. See also Chapter 3, Deploying Multiple Access Manager Instances.

This section also describes the following scenarios:

Configuring and Reconfiguring an Instance of Access Manager on UNIX and Linux Systems

You can configure an instance of Access Manager that was installed with the Configure Later option or reconfigure the first instance that was installed using Configure Now option in the Java Enterprise System installer by running the amconfig script. For example, you might want to reconfigure an instance to change the Access Manager owner and group.

The following steps apply to Solaris, HP-UX, and Linux systems.

ProcedureTo Configure or Reconfigure an Instance of Access Manager on UNIX and Linux Systems

  1. 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.

  2. 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 reconfigure an instance for Web Server 7, the following steps use an input file named amnewinstanceforWS7 in the /reconfig directory.

  3. In the amnewinstanceforWS7 file, set the DEPLOY_LEVEL variable to one of the values described for a Deployment Mode Variable operation.

    For example, set DEPLOY_LEVEL=21 to reconfigure a full installation.

  4. In the amnewinstanceforWS7 file, set the NEW_INSTANCE variable to false:


    NEW_INSTANCE=false

  5. Set other variables in the amnewinstanceforWS7 file to configure or reconfigure the instance.

    For example, to change the owner and group for the instance, set the NEW_OWNER and NEW_GROUP variables to their new values. For a description of other variables, refer to the tables in the following sections:

  6. 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 ./reconfig/amnewinstanceforWS7

    The -s option runs the script in silent mode. The amconfig script calls other configuration scripts as needed, using variables in the amnewinstanceforWS7 file to reconfigure the instance.

Configuring and Reconfiguring an Instance of Access Manager on Windows Systems

The following steps apply only to Windows systems.

ProcedureTo Configure or Reconfigure an Instance of Access Manager on Windows Systems

  1. Log in as an administrator, depending on the web container for the Access Manager instance.

  2. Make a copy of the AMConfigurator.properties silent configuration input file.

    For example: AMConfigurator-redeploy.properties

  3. In the new AMConfigurator-redeploy.properties file, set the DEPLOY_LEVEL variable to one of the values described for a Deployment Mode Variable operation.

    For example, set DEPLOY_LEVEL=21 to reconfigure a full installation.

  4. In the AMConfigurator-redeploy.properties file, set the NEW_INSTANCE variable to false.

  5. Set other variables in the AMConfigurator-redeploy.properties file to configure or reconfigure the instance.

    For a description of these variables, refer to the tables in the following sections:

  6. Edit the amconfig.bat file and change AMConfigurator.properties to AMConfigurator-redeploy.properties.

  7. Run amconfig.bat by double clicking on the file or executing the file from the Windows command prompt.

Uninstalling Access Manager on UNIX and Linux Systems

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.

ProcedureTo Uninstall an Instance of Access Manager on UNIX and Linux Systems

  1. 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.

  2. 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.

  3. 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.

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

Uninstalling Access Manager on Windows Systems

The following steps apply only to Windows systems.

ProcedureTo Uninstall an Instance of Access Manager on UNIX and Linux Systems

  1. Log in as an administrator, depending on the web container for the Access Manager instance.

  2. Make a copy of the AMConfigurator.properties silent configuration input file.

    For example: AMConfigurator-uninstall.properties

  3. In the new AMConfigurator-redeploy.properties file, set DEPLOY_LEVEL=11.

  4. Edit the amconfig.bat file as follows:

    • Change —configure to —unconfigure.

    • Change AMConfigurator.properties to AMConfigurator-uninstall.properties.

  5. Run amconfig.bat by double clicking on the file or executing the file from the Windows command prompt.

Uninstalling All Access Manager Instances

This scenario completely removes all Access Manager instances and packages from a system.

ProcedureTo Completely Remove Access Manager From a System

  1. Log in as or become superuser (root).

  2. In the input file you used to deploy the instance, 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.

  3. Run the amconfig script using the file you edited in Uninstalling All Access Manager Instances.

    For example, on Solaris systems with Access Manager installed in the default directory:

    # cd opt/SUNWam/bin/ 
# ./amconfig -s ./newinstances/amnewws7instance

    The amconfig script runs in silent mode to uninstall the instance.

    Repeat these steps for any other Access Manager instances you want to uninstall, except for the first instance, which is the instance you installed using the Java Enterprise System installer.

  4. To uninstall the first instance and remove all Access Manager packages from the system, run the Java Enterprise System uninstaller.

    For information about the uninstaller, refer to the Sun Java Enterprise System 5 Installation Guide for UNIX or the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows.