Flexible failover configuration

• US 9,432,240 B2
• Filed: 10/11/2013
• Issued: 08/30/2016
• Est. Priority Date: 04/29/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Galchev, Galin
• Primary Examiner(s): Winder, Patrice
• Assistant Examiner(s): TRAN, NAM T
• Application Number:
  US14/051,940
• Publication Number:
  US 20140040487A1
• Time in Patent Office: 1,054 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/2035 without idle spare hardware
• CPC Class Codes: G06F 11/2043 where the redundant components share a common memory address space
• CPC Class Codes: G06F 11/2046 where the redundant components share persistent storage G06F11/2043 takes precedence
• CPC Class Codes: H04L 65/1066 Session management
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

A method is described that involves offering a user different persistent scope choices including: a) internal to a computing system that the deployment descriptor is to be sent to; and, b) external to the computing system that the deployment descriptor is to be sent to. The method also involves offering a user different persistence frequency choices including: a) persisting per request; and, b) persisting per session state information attribute change. The method also involves generating a deployment descriptor that reflects the user'"'"'s choice of the persistence scope and persistence frequency.

Claims

1. A method comprising:

receiving a deployment descriptor that corresponds to an application and specifies whether a persistence scope of the application is instance-wide or cluster-wide;

if the deployment descriptor specifies that the persistence scope of the application is instance-wide, creating an instance-wide session domain that corresponds to the application based on the deployment descriptor specifying that the persistence scope is limited to one target computer, the instance-wide session domain being created on a target computer and configured to store session objects that represent sessions of the application, the instance-wide session domain corresponding to session criteria that include the persistence scope of the application;

otherwise, if the deployment descriptor specifies that the persistence scope of the application is cluster-wide, creating a cluster-wide session domain that corresponds to the application based on the deployment descriptor specifying that the persistence scope is for multiple target computers, the cluster-wide session domain being created on a target computer among a plurality of target computers accessible by the plurality of target computers to store session objects that represent sessions of the application, the cluster-wide session domain corresponding to session criteria that include the persistence scope of the application;

managing a session represented by a session object within the created session domain consistent with the session criteria that include the persistence scope of the application, the session interacting with the application; and

persisting state information of the session that interacts with the application based on he session criteria that include the persistence scope of the application, the persisting of the state information being performed by a processor of the target computer.

2. The method of claim 1, wherein:

the deployment descriptor specifies the session criteria that include the persistence scope of the application.

3. The method of claim 1, wherein:

the creating of the session domain configures the session domain to store the session criteria separately from session objects.

4. The method of claim 1, wherein:

the creating of the session domain configures the session domain to store session objects that contain no session criteria.

5. The method of claim 1, wherein:

the session actively services client requests to invoke the application that corresponds to the session domain.

6. The method of claim 1 further comprising:

determining that the persistence scope is limited to one target computer and that the target computer does not include a shared memory;

wherein

the persisting of the state information stores the state information on a file system internal to the target computer based on the persistence scope being limited to one target computer and on the target computer not including the shared memory.

7. The method of claim 1 further comprising:

determining that the persistence scope is limited to one target computer and that the target computer includes a shared memory;

wherein

the persisting of the state information stores the state information in the shared memory based on the persistence scope being limited to one target computer and based on the target computer including the shared memory.

8. The method of claim 1 further comprising:

determining that the persistence scope is for multiple target computers;

wherein

the persisting of the state information stores the state information in a database external to the target computer based on the persistence scope being for multiple target computers.

9. The method of claim 1, wherein:

the session criteria that includes the persistence scope further includes a persistence frequency that specifies persistence of the session information in response to a client request being processed within the session.

10. The method of claim 1, wherein:

the session criteria that includes the persistence scope further includes a persistence frequency that specifies persistence of the session information in response to a session state attribute being changed as a consequence of a client request being processed within the session.

11. The method of claim 1, wherein:

the session criteria that includes the persistence scope further includes at least one of a maximum inactive time interval, a maximum number of outstanding requests, or an access policy.

12. The method of claim 1, wherein:

the session criteria define how the session represented by session object is to be managed.

13. A non-transitory computer-readable memory comprising instructions that, when executed by one or more processors of a target computer, cause the target computer to perform operations comprising:

receiving a deployment descriptor that corresponds to an application and specifies whether a persistence scope of the application is instance-wide or cluster-wide;

if the deployment descriptor specifies that the persistence scope of the application is instance-wide, creating an instance-wide session domain that corresponds to the application based on the deployment descriptor specifying that the persistence scope is limited to one target computer, the instance-wide session domain being created on the target computer and configured to store session objects that represent sessions of the application, the instance-wide session domain corresponding to session criteria that include the persistence scope of the application;

otherwise, if the deployment descriptor specifies that the persistence scope of the application is cluster-wide, creating a cluster-wide session domain that corresponds to the application based on the deployment descriptor specifying that the persistence scope is for multiple target computers, the cluster-wide session domain being created on a target computer among a plurality of target computers accessible by the plurality of target computers to store session objects that represent sessions of the application, the cluster-wide session domain corresponding to session criteria that include the persistence scope of the application;

managing a session represented by a session object within the created session domain consistent with the session criteria that include the persistence scope of the application, the session interacting with the application; and

persisting state information of the session that interacts with the application based on the session criteria that include the persistence scope of the application.

14. The non-transitory machine-readable storage memory of claim 13, wherein:

the session criteria that includes the persistence scope further includes a persistence frequency that specifies persistence of the session information in response to a client request being processed within the session.

15. The non-transitory machine-readable storage memory of claim 13, wherein:

the session criteria that includes the persistence scope further includes a persistence frequency that specifies persistence of the session information in response to a session state attribute being changed as a consequence of a client request being processed within the session.

16. A system comprising:

a machine;

a computer readable medium comprising instructions that, when executed by one or more processors of the machine, cause the machine to perform operations that include;

receiving a deployment descriptor that corresponds to an application and specifies whether a persistence scope of the application is instance-wide or cluster-wide;

if the deployment descriptor specifies that the persistence scope of the application is instance-wide, creating an instance-wide session domain that corresponds to the application based on the deployment descriptor specifying that the persistence scope is limited to one target computer, the instance-wide session domain being created on the target computer and configured to store session objects that represent sessions of the application, the instance-wide session domain corresponding to session criteria that include the persistence scope of the application;

otherwise, if the deployment descriptor specifies that the persistence scope of the application is cluster-wide, creating a cluster-wide session domain that corresponds to the application based on the deployment descriptor specifying that the persistence scope is for multiple target computers, the cluster-wide session domain being created on a target computer among a plurality of target computers accessible by the plurality of target computers to store session objects that represent sessions of the application, the cluster-wide session domain corresponding to session criteria that include the persistence scope of the application;

managing a session represented by a session object within the created session domain consistent with the session criteria that include the persistence scope of the application, the session interacting with the application; and

persisting state information of the session that interacts with the application based on the session criteria that include the persistence scope of the application.

17. The system of claim 16, wherein:

the deployment descriptor specifies the session criteria that include the persistence scope of the application.

18. The system of claim 16, wherein the operations further include:

determining that the persistence scope is limited to one target computer and that the target computer does not include a shared memory;

wherein

the persisting of the state information stores the state information on a file system internal to the target computer based on the persistence scope being limited to one target computer and on the target computer not including the shared memory.

19. The system of claim 16, wherein the operations further include:

determining that the persistence scope is limited to one target computer and that the target computer includes a shared memory;

wherein

the persisting of the state information stores the state information in the shared memory based on the persistence scope being limited to one target computer and based on the target computer including the shared memory.

20. The system of claim 16, wherein the operations further include:

determining that the persistence scope is for multiple target computers;

wherein

the persisting of the state information stores the state information in a database external to the target computer based on the persistence scope being for multiple target computers.