System recovery

• US 7,650,606 B2
• Filed: 01/30/2004
• Issued: 01/19/2010
• Est. Priority Date: 01/30/2004
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Mathrubutham, Ramani, Sathye, Adwait, Ahuja, Pratima, Zou, Chendong
• Primary Examiner(s): Bullock, Jr.; Lewis A
• Assistant Examiner(s): To; Jennifer N
• Application Number:
  US10/768,328
• Publication Number:
  US 20050172288A1
• Time in Patent Office: 2,181 Days
• Field of Search: 718/101, 718/100, 718/106, 714/2, 714/10, 714/16, 707203-204, 705 7- 8, 705/39, 705/41
• US Class Current: 718/106
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating
• CPC Class Codes: G06Q 10/06316 Sequencing of tasks or work
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"

Abstract

Disclosed is a technique for system recovery. Information identifying one or more work requests is retrieved, along with an order of the work requests, for a business process. If the business process is non-transactional, an in-memory structure is created for the business process, a recovery stub is created for each work request, and the recovery stub for each work request is placed into the in-memory structure based on the order.

Claims

1. A method for system recovery, comprising:

retrieving information identifying one or more work requests, along with an order in which the work requests were received, for a business process;

wherein the information identifying the one or more work requests is retrieved by querying a log

determining that the business process is non-transactional, wherein a user creating the business process designates whether the business process is transactional or non-transactional; and

in response to determining that the business process is non-transactional,

creating an in-memory structure for the business process;

creating a recovery stub for each work request, wherein the recovery stub represents a portion of a corresponding work request and consists of a work request key that links together work requests, a work request ordering identifier that indicates the order in which the work request corresponding to the recovery stub was received, and a structure identifier that provides access to a complete work request stored in one or more transport structures corresponding to the business process;

wherein the recovery stub is created using the retrieving information from the log

placing the recovery stub for each work request into the in-memory structure based on the order; and

for each recovery stub, converting the recovery stub into a complete work request by retrieving the complete work request stored in the one or more transport structures, wherein the work request ordering identifier is used to locate the complete work request stored in the one or more transport structures.

2. The method of claim 1, further comprising:

accepting new work requests in the in-memory structure after processing each of the one or more identified work requests.

3. The method of claim 1, further comprising:

if the business process is transactional,

creating an in-memory structure for the business process;

creating a recovery stub for each work request, wherein the recovery stub indicates that rollback is to be performed; and

placing the recovery stub for each work request into the in-memory structure based on the order.

4. The method of claim 1, further comprising:

if the business process is transactional,

performing a rollback for each work request; and

creating an in-memory structure for the business process.

5. The method of claim 4, further comprising:

accepting new work requests in the in-memory structure after processing each of the one or more identified work requests.

6. The method of claim 1, further comprising:

retrieving an item from the in-memory structure; and

determining whether the item is the recovery stub.

7. The method of claim 6, wherein new work requests are being simultaneously received.

8. The method of claim 1, wherein the system is logically recovered to a consistent system state without executing the work requests that failed during system failure.

9. A computer readable medium storing a program for system recovery, wherein the program when executed by a processor of a computer causes operations to be performed, the operations comprising:

retrieving information identifying one or more work requests, along with an order in which the work requests were received, for a business process, wherein the information identifying the one or more work requests is retrieved by querying a log;

determining that the business process is non-transactional, wherein a user creating the business process designates whether the business process is transactional or non-transactional; and

in response to determining that the business process is non-transactional,

creating an in-memory structure for the business process;

creating a recovery stub for each work request, wherein the recovery stub represents a portion of a corresponding work request and consists of a work request key that links together work requests, a work request ordering identifier that indicates the order in which the work request corresponding to the recovery stub was received, and a structure identifier that provides access to a complete work request stored in one or more transport structures corresponding to the business process, wherein the recovery stub is created using the retrieved information from the log;

placing the recovery stub for each work request into the in-memory structure based on the order; and

for each recovery stub, converting the recovery stub into a complete work request by retrieving the complete work request stored in the one or more transport structures, wherein the work request ordering identifier is used to locate the complete work request stored in the one or more transport structures.

10. The computer readable medium of claim 9, wherein the operations further comprise:

accepting new work requests in the in-memory structure after processing each of the one or more identified work requests.

11. The computer readable medium of claim 9, wherein the operations further comprise:

if the business process is transactional,

creating an in-memory structure for the business process;

creating a recovery stub for each work request, wherein the recovery stub indicates that rollback is to be performed; and

placing the recovery stub for each work request into the in-memory structure based on the order.

12. The computer readable medium of claim 9, wherein the operations further comprise:

if the business process is transactional,

performing a rollback for each work request; and

creating an in-memory structure for the business process.

13. The computer readable medium of claim 12, wherein the operations further comprise:

accepting new work requests in the in-memory structure after processing each of the one or more identified work requests.

14. The computer readable medium of claim 9, wherein the operations further comprise:

retrieving an item from the in-memory structure;

determining whether the item is the recovery stub.

15. The computer readable medium of claim 14, wherein new work requests are being simultaneously received.

16. The computer readable medium of claim 9, wherein the system is logically recovered to a consistent system state without executing the work requests that failed during system failure.

17. A computer system having hardware logic for system recovery, wherein the hardware logic is executed by the computer system, the hardware logic comprising:

retrieving information identifying one or more work requests, along with an order in which the work requests were received, for a business process, wherein the information identifying the one or more work requests is retrieved by querying a log;

determining that the business process is non-transactional, wherein a user creating the business process designates whether the business process is transactional or non-transactional; and

in response to determining that the business process is non-transactional,

creating an in-memory structure for the business process;

creating a recovery stub for each work request, wherein the recovery stub represents a portion of a corresponding work request and consists of a work request key that links together work requests, a work request ordering identifier that indicates the order in which the work request corresponding to the recovery stub was received, and a structure identifier that provides access to a complete work request stored in one or more transport structures corresponding to the business process, wherein the recovery stub is created using the retrieved information from the log;

placing the recovery stub for each work request into the in-memory structure based on the order; and

for each recovery stub, converting the recovery stub into a complete work request by retrieving the complete work request stored in the one or more transport structures, wherein the work request ordering identifier is used to locate the complete work request stored in the one or more transport structures.

18. The computer system of claim 17, further comprising:

accepting new work requests in the in-memory structure after processing each of the one or more identified work requests.

19. The computer system of claim 17, further comprising:

if the business process is transactional,

creating an in-memory structure for the business process;

creating a recovery stub for each work request, wherein the recovery stub indicates that rollback is to be performed; and

placing the recovery stub for each work request into the in-memory structure based on the order.

20. The computer system of claim 17, further comprising:

if the business process is transactional,

performing a rollback for each work request; and

creating an in-memory structure for the business process.

21. The computer system of claim 20, further comprising:

accepting new work requests in the in-memory structure after processing each of the one or more identified work requests.

22. The computer system of claim 17, further comprising:

retrieving an item from the in-memory structure;

determining whether the item is the recovery stub.

23. The computer system of claim 22, wherein new work requests are being simultaneously received.

24. The computer system of claim 17, wherein the system is logically recovered to a consistent system state without executing the work requests that failed during system failure.