Application status board mitigation system and method

• US 7,954,062 B2
• Filed: 01/03/2005
• Issued: 05/31/2011
• Est. Priority Date: 01/03/2005
• Status: Active Grant

• Current Assignee: Hulu LLC (The Walt Disney Company)
• Original Assignee: International Business Machines Corporation
• Inventors: Jindani, Rahul, Burkhard, Scott D., Bright, Marion S., Scott, James D., Peachey-Kountz, Penny J., McKee, Gregory L.
• Primary Examiner(s): Huynh; Ba
• Assistant Examiner(s): Wiener; Eric
• Application Number:
  US10/905,403
• Publication Number:
  US 20060150105A1
• Time in Patent Office: 2,339 Days
• Field of Search: 715734-737, 715/772, 715965-970, 700 83- 85, 714 46- 48
• US Class Current: 715/772
• CPC Class Codes: G06F 11/0715 in a system implementing multitasking multitasking per se G06F9/46
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 11/3447 Performance evaluation by modeling
• CPC Class Codes: G06F 2201/88 Monitoring involving counting

Abstract

A system and method for monitoring computer applications comprising an application component table comprising a plurality of applications and application functions, wherein the applications comprise data identifying a functional status of the applications; a processor adapted to analyze the functional status of the applications based on the data; and a single status board user interface adapted to display the functional status of the applications, wherein the processor is adapted to predict when a running time of an application will be completed. The processor is adapted to determine whether the application functions fail when the applications are running; diagnose a cause of failure of the application functions; and indicate the cause of failure to a user. The processor is adapted to reconciliate information across processes supporting the applications. The system and method is adapted to send alerts to the single status board user interface of errors found in the processes.

Claims

1. A method of monitoring a plurality of application functions for a plurality of applications running across a plurality of computer systems in order to forecast the end of job streams, said method comprising:

storing, in memory on a server, a rules driven table defining said plurality of applications and said applications functions for each of said applications running across said plurality of computer systems, said application functions being capable of being monitored and said rules driven table specifying at least start times of application functions, estimated durations of application functions, and criteria for non-success of application functions;

when one of said application functions of one of said applications is invoked in a job-stream, receiving, by said server via a messaging service, an output comprising a data packet containing processing information specific to said one of said application functions;

analyzing, by a processor of said server and based on said rules driven table, said output to determine a functional status of said one of said application functions, said functional status comprising one of not successfully completed and successfully completed;

determining, by said processor and based on said functional status of said one of said application functions, on said rules driven table, and on historical data, projected completion times for other application functions of said one of said applications, said other application functions being in said job-stream and dependent upon said one of said application functions; and

displaying, on a user interface in communication with said server, an application status board for all of said applications running across said plurality of computer systems, said application status board indicating at least said functional status of said one of said application functions and said projected completion times for said other application functions of said one of said applications.

2. The method of claim 1, further comprising determining a progress of an order input into said plurality of computer systems within said network.

3. The method of claim 1, wherein said rules driven table comprises an application component table.

4. The method of claim 1, further comprising, based on said projected completion times, predicting when a running time of said one of said applications will be completed prior to actual completion of said running time.

5. The method of claim 1, wherein the analyzing process further comprises:

determining whether said one of said application functions failed during running of said one of said applications;

diagnosing a cause of failure of said one of said application functions; and

indicating said cause of failure to said user.

6. The method of claim 1, further comprising reconciling information across processes supporting said applications.

7. The method of claim 6, further comprising sending alerts to said user interface of errors found in said processes.

8. A method of monitoring a plurality of application functions for a plurality of applications running across a plurality of computer systems to mitigate job failures and forecast the end of job streams, said method comprising:

storing, in memory on a server, a rules driven application component table defining said plurality of applications and said applications functions for each of said applications running across said plurality of computer systems, said application functions being capable of being monitored and said rules driven application component table specifying at least start times of application functions, estimated durations of application functions and criteria for non-success of application functions;

when one of said application functions of one of said applications is invoked in a job-stream, receiving, by said server via a messaging service, an output comprising a data packet containing processing information specific to said one of said application functions;

analyzing, by a processor of said server and based on said rules driven application component table, said output to determine a functional status of said one of said application functions, said functional status comprising one of not successfully completed indicating an application function failure and successfully completed;

diagnosing, by said processor, a cause of said application function failure, when said application function failure is indicated;

determining, by said processor and based on said functional status of said one of said application functions, on said rules driven application component table, and on historical data, projected completion times for other application functions of said one of said applications, said other application functions being in said job-stream and dependent upon said one of said application functions; and

displaying, by a user interface in communication with said server, an application status board for all of said applications running across said plurality of computer systems, said application status board indicating at least said functional status of said one of said application functions, said cause of said application function failure, when said application function failure is indicated, and said projected completion times for said other application functions of said one of said applications.

9. The method of claim 8, further comprising, based on said projected completion times, predicting when a running time of said one of said applications will be completed prior to actual completion of said running time.

10. The method of claim 8, further comprising reconciling information across processes supporting said applications.

11. The method of claim 10, further comprising sending alerts to said user interface of errors found in said processes.