Configuring user session persistence
With the persistent session state feature, portal users can resume and continue a previously interrupted working session at the same state where they ended the session. When the user logs out or the session times out, the portal stores the current navigational state into the database. As a portal administrator you can give users the option to resume the navigational state of their last session when logging in again. When the user chooses to resume the last session, the navigational state stored previously is restored, and the user can continue working where the user stopped before.
About this task
Example: A user logs in and maximizes some portlets. Afterwards
the user logs out. When the user logs in again, all of the previously
maximized portlets are still maximized.
Note: Only the server side
aggregation (SSA) rendering mode supports user session persistence
to the full extent. Do not use the session persistence feature in
combination with the client side aggregation (CSA) rendering mode
of the Page
Builder theme.
If you use the session persistence feature with CSA, your users will
not have a consistent experience as to when and whether their session
is persisted or not. CSA reduces the amount of data sent between the
client and the server. Therefore the current navigational state of
the user session is synchronized with the server only by specific
user actions and is not persisted and restored by the server continuously.