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.

This section describes the following scenarios:

• Deploying Additional Instances of Access Manager

• Configuring and Reconfiguring an Instance of Access Manager

• Uninstalling Access Manager

• Uninstalling All Access Manager Instances

Deploying Additional Instances of Access Manager

Before you can deploy a new instance of Access Manager, you must create and start the new web container instance using the administration tools for the web container. For information, refer to the specific web container documentation:

• For Web Server, see http://docs.sun.com/coll/1308.1

• For Application Server, see http://docs.sun.com/coll/1310.1

The steps described in this section only apply to an Access Manager instance that has been installed with the Configure Now option. If you are planning to use WebLogic or WebSphere as web containers, you must use the Configure Later option when installing Access Manager. See Chapter 2, Installing and Configuring Third-Party Web Containers for more information.

Deploying an Additional Access Manager Instance

This section describes how to deploy an additional Access Manager instance on a different host server and update the Platform Server List.

To Deploy an Additional Access Manager Instance

1. Log in as an administrator, depending on the web container for the instance. For example, if Web Server 6.1 will be the web container for the new instance, log in either as superuser (root) or as the user account for the Web Server Administration Server.

2. Copy the amsamplesilent file to a writable directory and make that directory your current directory. For example, you might create a directory named /newinstances.

   Tip Rename the copy of the amsamplesilent file to describe the new instance you want to deploy. For example, the following steps use an input file named amnewws6instance to install a new instance for Web Server 6.1.

3. Set the following variables in the new amnewws6instance file:

   DEPLOY_LEVEL=1 NEW_INSTANCE=true

   Set other variables in the amnewws6instance file as required for the new instance you want to create. For a description of these variables, refer to the tables in the following sections:

   • Access Manager Configuration Variables

     • Web Container Configuration Variables

     • Directory Server Configuration Variables

       Important All Access Manager instances must use the same value for the password encryption key. To set the AM_ENC_PWD variable for this instance, copy the value from the am.encryption.pwd property in the AMConfig.properties file for the first instance.

       In case you might need to uninstall this instance later, save the amnewws6instance file.

4. Run the amconfig, specifying the new amnewws6instance file. For example, on Solaris systems:

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

   The -s option runs the amconfig script in silent mode.

   The amconfig script calls other configuration scripts as needed, using variables in the amnewws6instance file to deploy the new instance.

To Update the Platform Server List

When you crate an additional container instance, you must update the Access Manager Platform Server list to reflect the addition of the container(s).

1. Log in to the Access Manager Console as the top-level administrator.

2. Click on the Service Configuration tab.

3. Click on the Platform service.

4. Enter the following information for the new instance in the Server List:

   protocol://fqdn:port|instance-number

   The instance number should be the next available number that is not in use.

5. Click Add.

6. Click Save.

Configuring and Reconfiguring an Instance of Access Manager

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.

To Configure or Reconfigure an Instance of Access Manager

1. Log in as an administrator, depending on the web container for the instance. For example, if Web Server 6.1 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 6.1, the following steps use an input file named amnewinstanceforWS61 in the /reconfig directory.

3. In the amnewinstanceforWS61 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 amnewinstanceforWS61 file, set the NEW_INSTANCE variable to false:

   NEW_INSTANCE=false

5. Set other variables in the amnewinstanceforWS61 file to 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:

   • Access Manager Configuration Variables

     • Web Container Configuration Variables

     • Directory Server Configuration Variables

6. Run the amconfig script, specifying your edited input file. For example, on Solaris systems:

   # cd opt/SUNWam/bin/ # ./amconfig -s ./reconfig/amnewinstanceforWS61

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

Uninstalling Access Manager

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.

To Uninstall an Instance of Access Manager

1. Log in as an administrator, depending on the web container for the instance. For example, if Web Server 6.1 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 6.1, the following steps use an input file named amnewinstanceforWS61 in the /unconfigure directory.

3. In the amnewinstanceforWS61 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:

   # cd opt/SUNWam/bin/ # ./amconfig -s ./unconfigure/aminstanceforWS61

   The -s option runs the script in silent mode. The amconfig script reads the amnewinstanceforWS61 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 All Access Manager Instances

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

To Completely Remove Access Manager 7 2005Q4 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:

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

   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 2005Q4 Installation Guide for UNIX.