The following table describes how to install the components required for Access Manager session failover using the Java ES installer. If you are deploying an Access Manager WAR file, see Chapter 12, Deploying Access Manager as a Single WAR File.
Table 6–1 Installation of Access Manager Session Failover Components Using the Java ES Installer
Component |
Installation |
---|---|
Sun Java System Access Manager |
Install the first instance of Access Manager on each host server using the Java ES installer. The installer adds the required session failover Solaris packages or Linux RPMs. Installation reference: Sun Java Enterprise System 5 Installation Guide for UNIX or the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows When you install Access Manager using the Java ES installer, select either Realm Mode or Legacy Mode. Access Manager session failover is supported in both modes. After you run the Java ES installer, run the amconfig script to:
Reference: Chapter 3, Deploying Multiple Access Manager Instances |
Sun Java System Message Queue |
Install Message Queue using the Java ES installer. Installation reference: Sun Java Enterprise System 5 Installation Guide for UNIX or the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows Message Queue documentation: http://docs.sun.com/coll/1307.2 |
Session Failover Client Berkeley DB |
Install the Session Failover Client using the Java ES installer. On the installer Component Selection page, check Session Failover Client. The Java ES installer adds the Access Manager packages or RPMs required for the Berkeley DB and amsessiondb client:
You can install the Session Failover Client on a server that is running Access Manager; however, for improved performance, consider installing the subcomponent on a server that is not running Access Manager. |
In a multiple server deployment where all Access Manager instances share the same Directory Server, all Access Manager instances must use the same password encryption key value. When you install the first Access Manager instance, save the password encryption key value from the am.encryption.pwd property in the AMConfig.properties file. Then, when you run the Java ES installer or amconfig script to install or configure Access Manager instances on other host servers, use this same value for the password encryption key.