When session failover is implemented for Access Manager, session information is replicated in two backend session store databases. This ensures that when one Access Manager fails or stops, the information stored in the backend session databases can be used to keep the user continuously authenticated. If session failover is not implemented, when one Access Manager fails, if the user's session was created in the failed Access Manager server, the next time the user performs an operation that requires a session token, the user will have to use a login page to re-authenticate.
Use the following as your checklist for installing the Message Queue instances:
Access Manager provides a web container-independent session failover feature that uses Sun Java System Message Queue (Message Queue). Message Queue is a messaging middleware product that enables distributed applications to communicate and exchange data by sending and receiving messages. In this Deployment Example, Access Managers uses Message Queue as a communications broker, and uses the Berkeley DB by Sleepycat Software, Inc. for the backend session store databases.
For detailed information about how Access Manager and Message Queue interact, see Implementing Access Manager Session Failover in Sun Java System Access Manager 7 2005Q4 Deployment Planning Guide in the Access Manager Deployment Planning Guide.
The Java ES installer must be mounted on the host computer system where you will install Message Queue. See the section “To Download and Unpack the Java Enterprise System 2005Q4 Installer”3.2 Downloading and Mounting the Java Enterprise System 2005Q4 Installer in this document.
Log in as a root user to the host MessageQueue–1.
Start the installer with -nodisplay option. Example:
# cd /mnt/Solaris_sparc # ./installer -nodisplay
When prompted, provide the following information:
|
Press Enter. |
|
|
Press Enter. |
|
|
Enter 8 for English. |
|
|
Press Enter. |
|
|
Enter 12 for Message Queue. |
|
|
Press Enter. |
|
|
Accept the default value. |
|
|
Accept the default value. |
|
|
Enter 1 for Configure Now. |
|
|
First, see the following (Optional) Step 4. When you're ready to install, press Enter to accept the default value. |
|
|
Enter ! when you're ready to exit the installer program. |
(Optional) Monitor the log files and watch for installation errors.
# cd /var/sadm/install/logs # tail -f Java_Enterprise_System_install.B10110830 |
Log in as a root user to the host MessageQueue–2.
Start the installer with -nodisplay option. Example:
# cd /mnt/Solaris_sparc # ./installer -nodisplay
When prompted, provide the following information:
|
Press Enter. |
|
|
Press Enter. |
|
|
Enter 8 for English. |
|
|
Press Enter. |
|
|
Enter 12 for Message Queue. |
|
|
Press Enter. |
|
|
Accept the default value. |
|
|
Accept the default value. |
|
|
Enter 1 for Configure Now. |
|
|
First, see the following (Optional) Step 4. When you're ready to install, press Enter to accept the default value. |
|
|
Enter ! when you're ready to exit the installer program. |
(Optional) Monitor the log files and watch for installation errors.
# cd /var/sadm/install/logs # tail -f Java_Enterprise_System_install.B10110830 |