Session manager for web-based applications

• US 7,941,544 B2
• Filed: 03/18/2005
• Issued: 05/10/2011
• 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
• Primary Examiner(s): Avellino; Joseph E
• Assistant Examiner(s): Park; Jeong S
• Application Number:
  US11/082,871
• Publication Number:
  US 20060212589A1
• Time in Patent Office: 2,244 Days
• Field of Search: 709227-229
• US Class Current: 709/227
• 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 network including a plurality of servers executing a portal manager to maintain portal-based communication with a client terminal and a first application,

wherein the portal manager is configured to receive an authentication request directly from the client terminal and authenticate and admit the client terminal to the network and to establish a session between the requesting client terminal and the first application, wherein once the session is established, the first application is configured to communicate directly with the client terminal without communicating through the portal manager,

wherein the first application is configured to engage in interactive exchange with the client terminal and, after and in response to a period of no communication between the first application and the client terminal exceeding a predetermined length, send a termination message to the portal manager indicating that the session is invalid, and

wherein, in response to a second session being initiated between a second application and the client terminal, the second application delivers heartbeat messages at a predefined periodic rate to the portal manager, and in response to each heartbeat message, the portal manager sends an activity message to the first application, wherein receipt by the first application of the activity message at a predefined periodic rate prevents the first application from generating the termination message.

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 first application in response to the navigation 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 the first application corresponding to the new session identifier, the first application being configured to send the termination message to the termination address.

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 the termination message from the first application and to cause the session manager to remove a corresponding session ID from the session list.

5. The computer system of claim 1, wherein the first application maintains a timer that is reset by receipt of the activity message.

6. The computer system of claim 1,

wherein the first application does not authenticate the client terminal, and

wherein the termination address comprises a URL.

7. The computer system of claim 1, wherein the first application includes computer program instructions to determine if the period of no communication between the first application and the client terminal exceeds the predetermined length.

8. A computer system, comprising:

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

wherein the plurality of applications each invalidate a communication session with a client terminal and send a termination message to the portal manager indicating that the session is invalid after and in response to a predetermined period of no communication between the application and the client terminal, and communicate a refresh message to the portal manager during a predetermined period of communication 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 no communication with respect to the terminal.

9. The computer system of claim 8, 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, wherein the application is configured to send the termination message to the termination address.

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

11. The computer system of claim 8, 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, wherein the applications are configured to send the termination message to the termination address.

12. A communication management method, comprising:

responsive to a request directly from a terminal to a portal manager to invoke a first application, authenticating and assigning a session ID to a communication session between the terminal and the first application by the portal manager, the communication session being directly between the terminal and the first application without communicating through the portal manager,

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

adding the session ID to a session list,

communicating the session ID to the terminal by the portal manager, and

responsive to a termination message received from the first application at the portal manager at the termination address, the termination message indicating that the session is invalid and sent by the first application to the portal manager after and in response to a period of no communication between the first application and the client terminal exceeding a predetermined length, removing the session ID from the session list by the portal manager,

wherein, after a second session is initiated between a second application and the terminal, the portal manager receives heartbeat messages at a predefined periodic rate from the second application, and in response to each heartbeat message, the portal manager sends an activity message to the first application, wherein the sending by the portal manager of the activity message at a predefined periodic rate prevents the first application from generating the termination message.

13. The method of claim 12, further comprising authenticating the terminal.

14. The method of claim 13, further comprising, from the terminal, directly engaging the first application without requiring separate authentication with the first application.

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

16. The method of claim 12, wherein the termination message conforms to the SOAP protocol.

17. A communication method, comprising:

establishing multiple communication sessions each between a requesting agent and a respective application and authenticating the requesting agent by a central communication manager, each session associated with a predetermined inactivity timeout corresponding to a period of no communication between the requesting agent and the respective application and each session traversing a communication path that omits the central communication manager, wherein each application is configured to provide a termination message to the central communication manager after and in response to the predetermined inactivity timeout and indicating that the session is invalid,

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

18. The method of claim 17, 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, the first application being configured to send the termination message to the termination address,

adding the session ID to a session list, and

communicating the session ID to the terminal.

19. The method of claim 18, further comprising, before the establishing with a second application, communicating the session ID and a termination address to the second application, the second application being configured to send the termination message to the termination address.

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

21. A non-transitory computer-readable storage medium having program instructions, which, when executed by at least one processor in a network, perform a method, the method comprising:

receiving, from a client terminal, an authentication request at a portal manager running on the at least one processor;

authenticating, by the portal manager, a user of the client terminal in response to the authentication request from the client terminal;

receiving, at the portal manager from the client terminal, a session request for a session between the client terminal and a first application running on the network;

initiating, by the portal manager, the session between the client terminal and the first application;

receiving, directly by the first application from the client terminal without passing through the portal manager, session communications;

maintaining, by the first application, an inactivity timer having a value based on a length of time since a most recent session communication received at the first application from the client terminal;

upon the inactivity timer indicating that no session communications have been received, by the first application from the client terminal, for longer than a predetermined period of time, sending, from the first application to the portal manager, an inactivity termination message to communicate to the portal manager that the session between the first application and the client terminal is no longer valid;

receiving, from the client terminal, a second session request for a session between the client terminal and a second application running in the network;

initiating, by the portal manager, the session between the client terminal and the second application;

receiving, directly by the second application from the client terminal without passing through the portal manager, second session communications;

maintaining, by the second application, a refresh timer counting a second predetermined period of time;

upon receiving session communications, by the second application from the client terminal, within the second predetermined period of time, sending a heartbeat message by second application to the portal manager at the end of the second predetermined period of time;

upon receiving, by the portal manager, the heartbeat message from the second application, sending, by the portal manager, an activity message to the first application; and

upon receiving, by the first application, the activity message from the portal manager, resetting the inactivity timer so that it restarts measuring the time since a most recent session communication was received by the first application from the client terminal.