Siebel Self-Service Application Developer's Guide > Siebel Self-Service Application Architecture > About Session Handling in Self-Service Applications >

Failover

The session cookie can be persistent if the deploying company wants to use a failover mechanism. In failover mode, the Oracle ADF run time saves an additional browser cookie that the run time uses to track the latest passivation snapshot ID for each client running an application. Even though the user's next request will be processed in the context of a new HttpSession, perhaps even in a different application server instance, the user is unaware that this has occurred. The additional browser cookie is used to reactivate any available application module instance with the user's last pending state snapshot before handling the request.

Failover is configured at the application module level. For information on configuring failover, see Configuring Failover on the SessionAM Application Module. For information on data passivation and activation of the application module state, see Oracle Application Development Framework Developer's Guide For Forms/4GL Developers on Oracle Technology Network.