Shared memory implementations for session data within a multi-tiered enterprise network

• US 8,762,547 B2
• Filed: 04/29/2005
• Issued: 06/24/2014
• Est. Priority Date: 04/29/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Stanev, Georgi
• Primary Examiner(s): JAKOVAC, RYAN J
• Application Number:
  US11/118,890
• Publication Number:
  US 20060248200A1
• Time in Patent Office: 3,343 Days
• Field of Search: 709/228, 322/8
• US Class Current: 709/228
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

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 one embodiment, a representation of the hierarchy of session domains and data associated with the session objects is generated and managed within a shared memory. The session data is accessible from the shared memory by a plurality of different worker nodes within an application server.

Claims

1. A method comprising:

generating a plurality of session objects within a shared memory of an application server, each session object containing data defining a state of interaction between a specific client/application combination, the application server executing any combination'"'"'s particular application, said shared memory shared by a plurality of worker nodes within said application server, each of said worker nodes also having its own private memory within said application server;

organizing said session objects into hierarchies within said shared memory based on the applications of said application server that the session objects are generated in reference to, wherein, one hierarchy exists for each of said applications and each hierarchy includes a root node above lower session domain nodes having;

     1) corresponding session objects, and,

     2) different associated session management criteria; and

copying information that resides within a session domain from said shared memory into private memories of multiple worker nodes while keeping said information within said shared memory.

2. The method as in claim 1 further comprising:

generating a hierarchy of session objects for each of a plurality of operational layers within the application server.

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

EJB”

) container layer.

4. The method as in claim 3 further comprising:

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

5. The method as in claim 1 wherein each root node is designed to perform an operation on all of the root node'"'"'s lower session domain nodes.

6. The method as in claim 1 further comprising:

defining the session management criteria for each of the session domains.

7. The method as in claim 6 wherein the session management criteria includes an indication as to how long each of the session objects will remain in an active state following a client interaction.

8. The method as in claim 1 wherein the hierarchy comprises a system table for each session domain, the system table to store system data related to each session object within the session domain.

9. The method as in claim 8 further comprising:

copying the system table from the shared memory to a private memory of a worker node in response to detecting that the worker node needs access to session data, the worker node modifying the session data within the table and storing the system table back in the shared memory.

10. The method as in claim 9 wherein modifying the session data comprises removing data related to a session object from the table.

11. The method as in claim 8 wherein the system table is arranged with each row representing a different session object within each session domain.

12. The method as in claim 8 further comprising:

separating user data within the hierarchy from system data and logically separating the user data into a plurality of delta attributes, each of the delta attributes being independently accessible by each of the worker nodes.

15. The system as in claim 8 wherein the method further comprises defining the session management criteria for each of the session domains.

16. The system as in claim 8 wherein the method further comprises copying the system table from the shared memory to a private memory of a worker node in response to detecting that the worker node needs access to session data, the worker node modifying the session data within the table and storing the system table back in shared memory.

13. A system having memory coupled to one or more processors, said memory have program code that when executed by said processors causes said processors to perform a method, comprising:

generating a plurality of session objects within a shared memory of an application server, each session object containing data defining a state of interaction between a specific client/application combination, the application server executing any combination'"'"'s particular application, said shared memory shared by a plurality of worker nodes within said application server, each of said worker nodes also having its own private memory within said application server;

organizing said session objects into hierarchies within said shared memory based on the applications of said application server that the session objects are generated in reference to, wherein, one hierarchy exists for each of said applications and each hierarchy includes a root node above lower session domain nodes having;

     1) corresponding session objects, and,

     2) different associated session management criteria; and

copying information that resides within a session domain from said shared memory into private memories of multiple worker nodes while keeping said information within said shared memory.

14. The system as in claim 13 wherein each root node is to perform an operation on all of the root node'"'"'s lower session domain nodes.