Portal User Session Hibernation
Original Publication Date: 2003-Feb-20
Included in the Prior Art Database: 2003-Feb-20
AbstractThis document describes how user sessions can be tracked and restored in a portal area. This means that user specific customization is saved over several working sessions.
Portal User Session Hibernation
This document describes how user sessions can be tracked and restored in a portal area. This means that user specific customization is saved over several working sessions.
2 New Solution Objectives
The following scenarios/situations make the session hibernation necessary: A user interacts with the portal
* using a mobile phone. The connection is disrupted. Data which has so far been transferred to the portal is lost.
* using a web browser. He types in an e-mail, then changes a page. Then he logs of, forgetting the not yet sent e-mail. The typed text is lost.
* using a web browser. After coming back from lunch, his session has timed out (for security reasons). The individual session settings, including data which has been keyed into a portlet, is lost.
* using any device capable of displaying the portal. The device crashes, the user's session is disrupted. Individual session settings and keyed in data is lost.
Goal of the new solution is to offer a single point of access to a hibernation data store. The hibernation data store is used to securely keep user application data inside the Portal Server in case of failure, logoff or arbitrary other situations. The new solution embodies two types of hibernation:
* implicit and
* explicit hibernation The implicit hibernation is discussed in depth in chapter 5 of this document. It has already been implemented and is included in the WPO version 4, which will be available in April 2002. Implicit hibernation is executed by the Portal Server in the background, whenever on of the aforementioned situations occurs. The Portal Server automatically persistently saves the portal, the page and the portlet states. When the user logs in the next time and chooses to continue his session, the exact same state is reconstructed and presented to the user.
The explicit hibernation has not been implemented completely yet, but includes major parts of the invention. In this aspect of the invention, the portal server offers to all the portlet applications a common method through the Portlet API (a standardized Application Programming Interface to implement portlet applications). This common method is called by the portal on each and every portlet on the user's portal pages, when any of the above mentioned situations occurs. The portlet then has the ability to save any data which it needs to save. Upon the next login into the portal, this data is provided to the portlet by the Portal Server.
The combination of these two aspects allow the portal not to only recover the exact same state it was left in, but also to have each of the portlets inside the portal the exact same state as before. Which includes e.g. the half finished mail inside the mail-portlet.
3 The Portal User Session Hibernation
A portal is a collection of many single applications. A user connects to the portal server via a client and works with the applications. Every user performs
different tasks and...