Installing the Session Failover Components

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:

• Configure the first Access Manager instance, if you specified the Configure Later option during installation.

• Redeploy or reconfigure an installed Access Manager instance.

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:

• Solaris OS: SUNWamsfodb, SUNWbdb, and SUNWbdbj packages.

• Linux and HP-UX OS: sun-identity-sfodb, sun-berkeleydatabase-core, and sun-berkeleydatabase-java RPMs.

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.