Session manager for web-based applications

• US 20060212589A1
• Filed: 03/18/2005
• Published: 09/21/2006
• Est. Priority Date: 03/18/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Barwicki, Marek, Zimmermann, Patrick, Kohr, Timo, Hartmann, Joachim, Ohl, Jan, Hayer, Roman
• Granted Patent: US 7,941,544 B2
• Time in Patent Office: Days
• US Class Current: 709/229
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/28 Timers or timing mechanisms used in protocols
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A communication manager for web-based applications receives indications of application time outs via a callback mechanism. During session initiation, the communication manager provides a termination address to an application along with a session ID. If the session times out due to inactivity, the application may signal the communication manager that the session ID is invalid by sending a message to the termination address. Alternatively, when a communication manager establishes communication sessions for several applications with a common external terminal, the communication manager may receive messages identifying terminal activity at one of the applications and may signal to the other applications to keep their sessions active.

Claims

1. A computer system, comprising:

a plurality of networked servers executing a portal manager to maintain portal-based communication with client terminals and an application,

wherein the portal manager authenticates and admits client terminals to a network represented by the servers and to establish a session between a requesting client terminal and an identified application, the session to extend between the client terminal and the identified application but around the portal manager,

wherein the identified application engages in interactive exchange with the client terminal and, when a period of inactivity with the terminal exceeds a predetermined maximum limit, indicates to the portal manager that the session is invalid.

2. The computer system of claim 1, wherein the portal manager provides a navigation tool to the client terminal and the client terminal identifies the application in response to the tool.

3. The computer system of claim 1, wherein the portal manager comprises:

a communication manager provided in communication with the client terminal, and

a session manager to assign a new session identifier to a new session and to provide a termination address to applications corresponding to the new session identifier.

4. The computer system of claim 3, wherein the portal manager further comprises a callback manager having a network presence at the termination address, to field a termination message from an application and to cause the session manager to remove a corresponding session ID from the session list.

5. A computer system, comprising:

a plurality of networked servers executing a portal manager to maintain portal-based communication with client terminals and a plurality of applications,

wherein the applications each invalidate a communication session with a client terminal after a predetermined period of inactivity and communicate a refresh message to the portal manager during a predetermined period of activity with a client terminal, and

wherein, upon receipt of a refresh message from one application in communication with the client terminal, the portal manager causes other applications in communication with the same communication terminal to reset their measures of inactivity with respect to the terminal.

6. The computer system of claim 5, wherein the portal manager initiates a session between an application and the client terminal by providing a session ID to the application and the client terminal and by providing a termination address to the application.

7. The computer system of claim 6, wherein the portal manager comprises a callback manager having a network presence at the termination address, to field a termination message from the application and to cause the session manager to remove a corresponding session ID from its records.

8. The computer system of claim 5, wherein the portal manager comprises:

a communication manager provided in communication with the client terminal, and

a session manager to assign a new session identifier to a new session and to provide a termination address to applications corresponding to the new session identifier.

9. A communication management method, comprising:

responsive to a request from a terminal to invoke an application, assigning a session ID to a communication session between the terminal and the application,

communicating the session ID and a termination address to the application,

adding the session ID to a session list,

communicating the session ID to the terminal, and

responsive to a message received from the application at the termination address, removing the session ID from the session list.

10. The method of claim 9, further comprising authenticating the terminal.

11. The method of claim 10, further comprising, from the terminal, directly engaging the application without requiring separate authentication with the application.

12. The method of claim 9, wherein the termination message is transmitted to a URL specified in the termination address.

13. The method of claim 9, wherein the termination message conforms to the SOAP protocol.

14. A communication method, comprising, at a central communication manager:

establishing multiple communication sessions each between a requesting agent and a respective application, each session associated with a predetermined inactivity timeout and each session traversing a communication path that omits the communication manager,

responsive to a message from one application indicating ongoing activity with the requesting agent, communicating to other applications having active sessions with the requesting agent to refresh the inactivity timeout.

15. The method of claim 14, further comprising, before the establishing with a first application, assigning a session ID to a communication session between the terminal and the applications,

communicating the session ID and a termination address to the first application,

adding the session ID to a session list, and

communicating the session ID to the terminal.

16. The method of claim 15, further comprising, before the establishing with a second application, communicating the session ID and a termination address to the second application.

17. The method of claim 14, further comprising, upon expiration of the inactivity timeout at one of the applications, communicating a termination message to a callback manager.