Session management within a multi-tiered enterprise network

• US 8,204,931 B2
• Filed: 12/28/2004
• Issued: 06/19/2012
• Est. Priority Date: 12/28/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Stanev, Georgi, Galchev, Galin
• Primary Examiner(s): Jakovac, Ryan
• Application Number:
  US11/025,200
• Publication Number:
  US 20060143217A1
• Time in Patent Office: 2,730 Days
• Field of Search: 709/203
• US Class Current: 709/203
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A system and method are described in which session objects are organized and managed within a structured hierarchy of session object storage units, referred to herein as “session domains.” The session domains store session objects sharing one or more related characteristics. In one embodiment, a separate hierarchy of session domains is implemented within each layer of an enterprise application server. For example, in a Java 2 Enterprise Edition (“J2EE”) environment, a separate set of hierarchically-arranged session domains are generated for the EJB container, the Web container and the portal container. In addition, in one embodiment of the invention, the lifecycles of each of the session objects are managed based on the relationships between each of the session objects. The relationships may either be explicit or implicit. In the latter case, one embodiment of the invention detects the relationship, automatically declares the relationship, and uses the relationship to manage the lifecycle of the related sessions.

Claims

1. A method comprising:

generating, using one or more processors, a plurality of session objects at an application server in response to client requests, the session objects storing session data defining a state of interaction with each of a respective plurality of clients;

defining a structured hierarchy of session domains within the application server, the session domains to organize session objects having one or more related characteristics;

grouping, using the one or more processors, related session domains within one of a plurality of hierarchy levels based on the one or more related characteristics of each of the session objects; and

defining a configuration policy for each of the session domains, the configuration policy including parameters for managing session objects within each session domain, the defining the configuration policy also including defining;

a set of local storage attributes for each of the session domains, the local storage attributes defining storage parameters for storing the session objects within a virtual machine on which the session objects are originally created and executed; and

a set of global storage attributes for each of the session domains, the global storage attributes defining storage parameters for storing the session objects within a shared memory accessible by multiple local virtual machines.

2. The method as in claim 1 wherein defining further comprises:

generating a separate hierarchy of session domains for each of a plurality of layers within the application server.

3. The method as in claim 2 wherein the layers include an enterprise java bean (“

EJB”

) container.

4. The method as in claim 3 wherein defining further comprises:

generating a separate session domain for each session bean within the EJB container.

5. The method as in claim 1 wherein defining further comprises:

generating a separate set of hierarchies of session domains for each of a plurality of applications executed by the application server.

6. The method as in claim 5 wherein generating the separate set of hierarchies of session domains further comprises:

generating a separate hierarchical tree of session object storage units for each of a plurality of layers within the application server.

7. The method as in claim 1 wherein the session domains represent abstract storage units for session objects that have similar characteristics, the session domains are organized within a hierarchy under a session context.

8. The method as in claim 1 wherein the configuration policy includes an indication as to how long each of the session objects will remain in an active state following a client interaction.

9. The method as in claim 1 wherein one of the characteristics used to group the session objects is that each of the session objects exists in a same application server layer for a same application.

10. The method as in claim 1 further comprising:

subdividing each of the session objects into a user part and a system part, the user part to store user data associated with each session and the system part to store session management data.

11. The method as in claim 10 further comprising:

receiving session requests from applications and a container, the requests associated with a particular session object;

providing only the user part of the session object in response to session requests from applications; and

providing only the system part of the session objects in response to session requests from the container.

12. The method as in claim 10 further comprising:

storing the user part in a first storage location within the application server; and

storing the system part in a second storage location within the application server.

13. The method as in claim 12 further comprising:

optimizing the second storage location for read access relative to the first storage location.

14. A system comprising:

a server including one or more processors and coupled to a network, the one or more processors executing;

a plurality of worker nodes communicatively coupled to the network to serve applications over the network to a plurality of clients, the worker nodes generating a plurality of session objects in response to client requests, the session objects storing session data defining a state of interaction with each of a respective plurality of clients; and

a session manager to,

generate a hierarchy of session object storage units, the session object storage units to store session objects having one or more related characteristics, the session manager to group the session objects within the session object storage units based on the one or more related characteristics of each of the session objects,

define a configuration policy object associated with each of the session object storage units, the configuration policy object including parameters for managing session objects within each session object storage unit,

define a set of local storage attributes for each of the session domains, the local storage attributes defining storage parameters for storing the session objects within a virtual machine on which the session objects are originally created and executed, and

define a set of global storage attributes for each of the session domains, the global storage attributes defining storage parameters for storing the session objects within a shared memory accessible by multiple local virtual machines.

15. The system as in claim 14 wherein the session manager generates a separate hierarchy of session object storage units for each of a plurality of layers within an enterprise application server.

16. The system as in claim 15 wherein the layers include an enterprise java bean (“

EJB”

) container.

17. The system as in claim 16 wherein generating further comprises:

generating a separate session object storage unit for each session bean within the EJB container.

18. The system as in claim 14 wherein generating further comprises:

generating a separate set of hierarchies of session object storage units for each of a plurality of applications executed by an application server.

19. The system as in claim 18 wherein generating the separate set of hierarchies of session object storage units further comprises:

generating a separate hierarchical tree of session object storage units for each of a plurality of layers within an enterprise application server.

20. The system as in claim 14 wherein the session object storage units comprise session domains.

21. The system as in claim 14 wherein the configuration policy object includes an indication as to how long each of the session objects will remain in an active state following a client interaction.

22. The system as in claim 14 wherein one of the characteristics used to group the session objects is that each of the session objects exists in the same application server layer for the same application.

23. The system as in claim 14 further comprising:

subdividing each of the session objects into a user part and a system part, the user part to store user data associated with each session and the system part to store session management data.

24. The system as in claim 23 wherein the session manager receives session requests from applications and a container, the requests associated with a particular session object;

provides only the user part of the session object in response to session requests from applications; and

provides only the system part of the session objects in response to session requests from the container.

25. The system as in claim 23 wherein the session manager stores the user part in a first storage location within an application server;

and stores the system part in a second storage location within the application server.

26. The system as in claim 25 wherein the second storage location is optimized for read access relative to the first storage location.

27. The system as in claim 25 wherein the first storage location comprises persistent storage and wherein the second storage location comprises random access memory.

28. A non-transitory machine-readable storage medium having program code stored thereon which, when executed by a machine, cause the machine to perform the operations of:

generating a plurality of session objects in response to client requests, the session objects storing session data defining a state of interaction with each of a respective plurality of clients;

defining a hierarchy of session object storage units, the session object storage units to store session objects having one or more related characteristics;

grouping the session objects within the session object storage units based on the one or more related characteristics of each of the session objects; and

defining a configuration policy for each of the session object storage units, the configuration policy including parameters for managing session objects within each session object storage unit, the defining the configuration policy including defining;

a set of local storage attributes for each of the session domains, the local storage attributes defining storage parameters for storing the session objects within a virtual machine on which the session objects are originally created and executed; and

a set of global storage attributes for each of the session domains, the global storage attributes defining storage parameters for storing the session objects within a shared memory accessible by multiple local virtual machines.

29. The non-transitory machine-readable storage medium as in claim 28 wherein defining further comprises:

generating a separate hierarchy of session object storage units for each of a plurality of layers within an enterprise application server.

30. The non-transitory machine-readable storage medium as in claim 29 wherein the layers include an enterprise java bean (“

EJB”

) container.

31. The non-transitory machine-readable storage medium as in claim 30 wherein defining further comprises:

generating a separate session object storage unit for each session bean within the EJB container.

32. The non-transitory machine-readable storage medium as in claim 28 wherein defining further comprises:

generating a separate set of hierarchies of session object storage units for each of a plurality of applications executed by an application server.

33. The non-transitory machine-readable storage medium as in claim 32 wherein generating the separate set of hierarchies of session object storage units further comprises:

generating a separate hierarchical tree of session object storage units for each of a plurality of layers within an enterprise application server.

34. The non-transitory machine-readable storage medium as in claim 28 wherein the session object storage units comprise session domains.

35. The non-transitory machine-readable storage medium as in claim 28 wherein the configuration policy includes an indication as to how long each of the session objects will remain in an active state following a client interaction.

36. The non-transitory machine-readable storage medium as in claim 28 wherein one of the characteristics used to group the session objects is that each of the session objects exists in the same application server layer for the same application.

37. The non-transitory machine-readable storage medium as in claim 28 including additional program code to cause the machine to perform the operations of:

subdividing each of the session objects into a user part and a system part, the user part to store user data associated with each session and the system part to store session management data.

38. The non-transitory machine-readable storage medium as in claim 37 including additional program code to cause the machine to perform the operations of:

receiving session requests from applications and a container, the requests associated with a particular session object;

providing only the user part of the session object in response to session requests from applications; and

providing only the system part of the session objects in response to session requests from the container.

39. The non-transitory machine-readable storage medium as in claim 37 including additional program code to cause the machine to perform the operations of:

storing the user part in a first storage location within an application server; and

storing the system part in a second storage location within the application server.

40. The non-transitory machine-readable storage medium as in claim 39 including additional program code to cause the machine to perform the operations of:

optimizing the second storage location for read access relative to the first storage location.