SYNCHRONIZING PROBLEM RESOLUTION TASK STATUS USING AWARENESS OF CURRENT STATE AND TRANSACTION HISTORY

• US 20110055619A1
• Filed: 09/01/2009
• Published: 03/03/2011
• Est. Priority Date: 09/01/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: SCHREIBER, ELIZABETH A., COURT, BARNABY L., BHATNAGAR, RADHIKA, STYLES, DAVID B., KUNDAVARAM, ANJAN R., ETGEN, MICHAEL P.
• Granted Patent: US 9,384,080 B2
• Time in Patent Office: Days
• US Class Current: 714/2
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40

Abstract

Systems, methods and articles of manufacture are disclosed for synchronizing a transaction profile with a resolution status of a problem experienced by an application. The problem may be detected for the application. A transaction profile may be retrieved for the detected problem. The transaction profile may include a sequence of transactions to be performed on the system to remedy the open problem. Transactions occurring on the system may be monitored, and an instance of the transaction profile may be updated accordingly to create a synchronized transaction profile.

Claims

1. A computer-implemented method, comprising:

configuring one or more computer processors of a system to perform an operation comprising;

identifying a problem experienced by an application executing on the system,

retrieving a transaction profile associated with the problem, wherein the transaction profile specifies a sequence of transactions to be performed on the system to resolve the problem,

monitoring transactions occurring on the system, and

upon detecting that a transaction occurring on the system matches one of the sequence of transactions of the transaction profile, marking the one of the sequence of transactions in the transaction profile as having been performed.

2. The computer-implemented method of claim 1, wherein monitoring transactions occuring on the system includes at least one of:

(i) logging a transaction performed on the system by a user;

(ii) listening for an event of the system;

(iii) listening for an event of the application;

(iv) listening for an event of another application executing on the system; and

(v) running a verification script to determine a status of the application.

3. The computer-implemented method of claim 2, wherein the application and the another application execute in a single application stack on the system.

4. The computer-implemented method of claim 1, wherein the operation further comprises:

upon determining that the marked one of the sequence of transactions completes the seqeunce of transactions to be performed on the system to remedy the problem, setting the status of the problem as closed.

5. The computer-implemented method of claim 1, wherein the operation further comprises:

notifying a user that the one of the sequence of transactions in the transaction profile is performed.

6. The computer-implemented method of claim 1, wherein the detected transaction is initiated by a user of the system, wherein the detected transaction does not complete the sequence of transactions, and wherein the operation further comprises:

notifying the user of remaining transactions of the sequence of transactions that are to be performed on the system to remedy the problem.

7. The computer-implemented method of claim 1, wherein the operation further comprises:

receiving a request from a user to perform a transaction on the system;

upon determining that the transaction requested by the user matches the marked one of the sequence of transactions in the transaction profile, asking the user to verify that the transaction is to be performed.

8. A computer-readable storage medium containing a program which, when executed, performs an operation comprising:

identifying a problem experienced by an application executing on the system;

retrieving a transaction profile associated with the problem, wherein the transaction profile specifies a sequence of transactions to be performed on the system to resolve the problem;

monitoring transactions occurring on the system; and

upon detecting that a transaction occurring on the system matches one of the sequence of transactions of the transaction profile, marking the one of the sequence of transactions in the transaction profile as having been performed.

9. The computer-readable storage medium of claim 8, wherein monitoring transactions occuring on the system includes at least one of:

(i) logging a transaction performed on the system by a user;

(ii) listening for an event of the system;

(iii) listening for an event of the application;

(iv) listening for an event of another application executing on the system; and

(v) running a verification script to determine a status of the application.

10. The computer-readable storage medium of claim 9, wherein the application and the another application execute in a single application stack on the system.

11. The computer-readable storage medium of claim 8, wherein the operation further comprises:

upon determining that the marked one of the sequence of transactions completes the seqeunce of transactions to be performed on the system to remedy the problem, setting the status of the problem as closed.

12. The computer-readable storage medium of claim 8, wherein the operation further comprises:

notifying a user that the one of the sequence of transactions in the transaction profile is performed.

13. The computer-readable storage medium of claim 8, wherein the detected transaction is initiated by a user of the system, wherein the detected transaction does not complete the sequence of transactions, and wherein the operation further comprises:

notifying the user of remaining transactions of the sequence of transactions that are to be performed on the system to remedy the problem.

14. The computer-readable storage medium of claim 8, wherein the operation further comprises:

receiving a request from a user to perform a transaction on the system;

upon determining that the transaction requested by the user matches the marked one of the sequence of transactions in the transaction profile, asking the user to verify that the transaction is to be performed.

15. A system, comprising:

one or more computer processors; and

a memory containing a program, which when executed by the one or more computer processors is configured to perform an operation, comprising;

identifying a problem experienced by an application executing on the system,

retrieving a transaction profile associated with the problem, wherein the transaction profile specifies a sequence of transactions to be performed on the system to resolve the problem,

monitoring transactions occurring on the system, and

upon detecting that a transaction occurring on the system matches one of the sequence of transactions of the transaction profile, marking the one of the sequence of transactions in the transaction profile as having been performed.

16. The system of claim 15, wherein monitoring transactions occuring on the system includes at least one of:

(i) logging a transaction performed on the system by a user;

(ii) listening for an event of the system;

(iii) listening for an event of the application;

(iv) listening for an event of another application executing on the system; and

(v) running a verification script to determine a status of the application.

17. The system of claim 16, wherein the application and the another application execute in a single application stack on the system.

18. The system of claim 15, wherein the operation further comprises:

upon determining that the marked one of the sequence of transactions completes the seqeunce of transactions to be performed on the system to remedy the problem, setting the status of the problem as closed.

19. The system of claim 15, wherein the operation further comprises:

notifying a user that the one of the sequence of transactions in the transaction profile is performed.

20. The system of claim 15, wherein the detected transaction is initiated by a user of the system, wherein the detected transaction does not complete the sequence of transactions, and wherein the operation further comprises:

notifying the user of remaining transactions of the sequence of transactions that are to be performed on the system to remedy the problem.

21. The system of claim 15, wherein the operation further comprises:

receiving a request from a user to perform a transaction on the system; and

upon determining that the transaction requested by the user matches the marked one of the sequence of transactions in the transaction profile, asking the user to verify that the transaction is to be performed.