To Remove a Session Failover Configuration

1. In the Access Manager Administration Console, remove the session failover configuration (that is, the secondary configuration under Session Service in the Console).

2. Restart all the Access Manager servers participating in the cluster.

3. Shutdown the Message Queue broker instances and amsessiondb instances using the amsfo script on the target systems.

   For more information, see Running the amsfo Script.

4. In the web container server.xml file, remove the installed locations of the imq.jar and jms.jar files. For example:

   <JAVA javahome="/usr/jdk/entsys-j2se" serverclasspath=
   "/usr/share/lib/imq.jar:/usr/share/lib/jms.jar:
   /opt/SUNWwbsvr/bin/https/jar/webserv-rt.jar:
   ${java.home}/lib/tools.jar:
   /opt/SUNWwbsvr/bin/https/jar/webserv-ext.jar:
   /opt/SUNWwbsvr/bin/https/jar/webserv-jstl.jar:
   /usr/share/lib/ktsearch.jar"

5. Optionally, uninstall the Message Queue and Berkeley DB components from the target systems.

Next Steps

Several other considerations are:

• After you remove the session failover configuration, determine whether you also want to remove the site configuration for the deployment. If you keep the site configuration without session failover, session constraints (if configured) are not supported.

• If the cookie encoding setting on the Access Manager server side is restored, the corresponding setting of the cookie encoding for a remote client might also need to be restored.