To Configure Host B: Example Sequence

Before You Begin

• Access Manager core services must be installed and running on a remote host (Host A).

• Web container information and Directory Server configuration information that you provide in this installation example must match the web container and Directory Server configuration information that you provided during installation of Access Manager core services.

The Java ES installer does not allow you to configure the web container when you are installing only the Access Manager SDK.

1. Check the installation sequence guidelines.

   Check which guidelines apply to this example and make adjustments as needed. Refer to Table 2–1.

2. Check the installation prerequisites.

   Check which tasks you might need to perform for this installation before starting. Refer to Table 1–1.

3. Run the Java ES installer.

4. Accept licence agreement and select the destination folder for installation.

5. Choose the type of installation, select Custom.

6. Select the Configure Manually After Installation type.

7. At component selection, choose Access Manager SDK.

8. Resolve incompatibilities.

   The installer verifies software on your host and provides guidance if incompatibilities are identified.

9. Type administrator user name and password.

10. Run the installation.

11. View the Installation Summary and Log.

12. Configure and start web container administration server.

    For more information about configuring web container, see Chapter 5, Completing Postinstallation Configuration.

13. Edit the AccessManager-base\setup\AMConfigurator.properties file.

    Modify the following parameters in the AMConfigurator.properties file:

    • Set DEPLOY_LEVEL to 4.

    • Set SERVER_HOST and SERVER_PORT to the host and port of the full server which will be used by Access Manager SDK.

    • Set DS_HOST, DS_DIRMGRPASSWD, and ROOT_SUFFIX to the hostname, directory manager password, and root suffix of the Host A Directory Server.

    • Set ADMINPASSWD and AMLDAPUSERPASSWD to the amadmin and amldapuser passwords used on Host A.

    • Set AM_ENC_PWD to the password encryption key used on Host A. For the Access Manager SDK, use the same encryption key for AM_ENC_PWD as the encryption key specified during the remote installation of Access Manager on Host B. Use the following command to obtain this value: Accessmanager-base/config/AMConfig.properties

    • Set WEB_CONTAINER to the corresponding value for the web container being used.

    • Set BASEDIR to the install directory used during the Configure Manually After Installation of Access Manager SDK.

    • Set AM_REALM to Enabled if realm mode is used on Host A, and Disabled if legacy mode is used on Host A.

    • Find the settings corresponding to the web container that will be used for the SDK and modify these settings with the details of the web container. For example, if WEB_CONTAINER is set to WS6 (Sun Java System Web Server), then you should modify the settings that are prefixed by WS61 (WS61_INSTANCE , WS61_HOME, WS61_PROTOCOL and so on.

14. As administrator, use the edited AMConfigurator.propertiesfile to deploy Access Manager.

    AccessManager-base\setup\amconfig.bat