Apparatus and method to detect and track software installation errors

• US 8,589,914 B2
• Filed: 05/19/2011
• Issued: 11/19/2013
• Est. Priority Date: 02/15/2007
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Wookey, Michael J.
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): Lee, Marina
• Application Number:
  US13/111,340
• Publication Number:
  US 20110225461A1
• Time in Patent Office: 915 Days
• Field of Search: 717168-178, 717120-121, 714 25- 473
• US Class Current: 717/175
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates

Abstract

A virtual installation map, and method involving installing a software functionality using the same, the virtual installation map including a first software installation map including a plurality of software elements representative of a related software file, the software elements also including at least one dependency to another software element. The virtual installation map further including a second software installation map also including a second plurality of software elements representative of related software file along with related dependencies. The first and second software installation maps may be hosted in separate databases and may relate to software products provided by different vendors. One or both software installation maps may include a pointer or other reference to the other installation map thereby providing a virtual installation map, in one example.

Claims

1. A system for managing software installation errors comprising:

a service provider module stored on and executed by a processing device for hosting a software installation map, the software installation map comprising;

a plurality of software elements, wherein each of the plurality of software elements represents one of a plurality of software files;

a plurality of dependency pointers representing a plurality of dependencies between the plurality of software files;

at least one software installation route describing a subset of the plurality of software files combinable to represent at least one software functionality; and

a confidence factor associated with the plurality of dependency pointers indicating at least a number of a plurality of successful prior installations involving the at least one software installation route;

the service provider module configured to provide the software installation route to a client device to install the subset of the plurality of software files; and

an error analysis module in communication with the service provider module, the error analysis module configured to analyze an error message received from the client device in association with the software installation route for installing the subset of the plurality of software files.

2. The system of claim 1 wherein the error analysis module is configured to perform the operations of:

analyzing the error message to determine a source of the error message;

associating the received error and a timestamp of when the error occurred with at least one of the plurality of software elements responsible for the error; and

associating the received error with the software installation route used for installing the software functionality.

3. The system of claim 2 wherein the error analysis module is configured to perform the operations of:

analyzing the error message to identify files installed on the client device prior to the installation of the subset of the plurality of software files.

4. The system of claim 2 wherein the confidence factor represents an estimate of whether the at least one software installation route will provide for a successful installation of the software functionality.

5. The system of claim 4 wherein the operation of associating the received error with the software installation route used for installing the software functionality further comprises:

associating information about the received error with the software installation route; and

reducing the confidence factor associated with the software installation route.

6. The system of claim 5 where the operation of reducing the confidence factor associated with the software installation route is determined by dividing a number of installations based on the software installation route by a number of successful installations based on the software installation route.

7. A method for managing software installation errors comprising:

providing a software installation route to a client device for installing a software functionality, wherein the software installation route describing a subset of a plurality of software files combinable to represent the software functionality, comprises;

a plurality of software elements, wherein each of the plurality of software elements represents one of the plurality of software files, a plurality of dependency pointers representing a plurality of dependencies between the plurality of software files and a confidence factor associated with the plurality of dependency pointers indicating at least a number of a plurality of successful prior installations involving the software installation route;

receiving an error string associated with the software installation route;

parsing the error string to determine a cause of the error;

associating the received error with a software element associated with the error; and

associating the received error with the software installation route used for installing the software functionality.

8. The method of claim 7 further comprising:

parsing the error string to further determine a time of the error; and

associating the received error and the time of the error with the software element associated with the error.

9. The method of claim 8 wherein parsing the error string further comprises:

identifying references to any files that may have already been installed on the client device prior to the installation; and

identifying references to any known installation problems.

10. The method of claim 9 wherein the confidence factor represents an estimate that the software installation route will provide for a successful installation.

11. The method of claim 10 wherein associating the received error with the software installation route used for installing the software functionality further comprises:

attaching information about the received error to the software installation route; and

reducing the confidence factor associated with the software installation route as a function of the received error.

12. The method of claim 11 wherein reducing the confidence factor associated with the software installation route involves dividing a number of uses of the software installation route by a number of successful installations provided by the software installation route.

13. The method of claim 11 wherein associating the received error with the software installation route further comprises:

associating the software element responsible for the error with the software installation route;

associating the error string with the software installation route; and

associating a cause of the error with the software installation route.

14. The method of claim 8 wherein the error string is transmitted by a software agent installed on the client device.

15. The method of claim 7 further comprising:

providing details of the parsed error string to the client device.

16. The method of claim 7, further comprising:

revising the software installation route to avoid the cause of the error.

17. The method of claim 16, further comprising:

providing a revised software installation route to the client device.

18. A method for transmitting software installation errors, comprising:

upon a request for installing a software functionality, receiving a software installation route from a service provider module, the software installation route describing a subset of a plurality of software files combinable to represent the software functionality, comprising a plurality of software elements, wherein each of the plurality of software elements represents one of the plurality of software files for installing the software functionality, and a plurality of dependency pointers representing a plurality of dependencies between the plurality of software files and a confidence factor associated with the plurality of dependency pointers indicating at least a number of a plurality of successful prior installations involving the software installation route;

installing at least one software file based on the software installation route on a client device;

receiving an installation error message associated with the software installation route; and

transmitting the installation error message to the service provider module.

19. The method of claim 18 further comprising providing a software agent on the client device to perform transmitting software installation errors of claim 18.

20. The method of claim 18, further comprising:

receiving a revised software installation route.