APPARATUS AND METHOD FOR INSTALLING SOFTWARE USING A SOFTWARE DEPENDENCY MAP

• US 20110231838A1
• Filed: 05/26/2011
• Published: 09/22/2011
• 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.
• Granted Patent: US 8,621,453 B2
• Time in Patent Office: Days
• US Class Current: 717/178
• 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 method for installing software on a computing device comprising:

receiving, at a service provider, a first software installation request to install a first software functionality;

accessing a software installation map comprising;

a plurality of software elements representing a plurality of software files, a subset of the plurality of software elements associated with the first software functionality;

a plurality of dependency pointers identifying functional dependencies between the plurality of software files;

determining at least one installation route for installing the first software functionality, the at least one installation route identifying the subset of the plurality of software elements; and

providing the installation route to a computing device.

2. The method of claim 1 further comprising:

transmitting the at least one installation route to the computing device over a communication network.

3. The method of claim 1 wherein the operation of receiving a first software installation request further comprises:

receiving a first installation criteria for installing the first software functionality.

4. The method of claim 3 wherein the software installation map includes indicators representative of operating speed of the software functionality, error rate of the software functionality, and version of the software functionality and wherein the first installation criteria is a function of at least one of the following factors:

operating speed of the software functionality, stability of the software functionality, and version of the software functionality.

5. The method of claim 1 wherein the software installation map further comprises:

a first installation route including at least a first subset of the plurality of software elements to install the first software functionality; and

a second installation route including at least a second subset of the plurality of software elements, the second subset differing from the first subset by at least one software element, the second subset of software elements to install the first software functionality.

6. The method of claim 5 wherein the operation of determining the at least one install route further comprises:

selecting a preferred installation route from at least the first and second installation route.

7. The method of claim 5 wherein the first installation route has a first confidence factor being a function of a historical record of previous installations based on the first installation route and the second installation route has a second confidence factor being a function of a historical record of previous installations based on the second installation route.

8. The method of claim 7 wherein the first and second confidence factors represent an estimate of whether the first and second installation routes, respectively, will result in a successful installation of the first software functionality on the computing device.

9. The method of claim 6 wherein the operation of selecting a preferred installation route is a function of at least the first and second confidence factors.

10. The method of claim 1 further comprising:

providing the software files to the computing device, the software files associated with each software element identified in the installation route.

11. The method of claim 1 wherein each of the plurality of dependency pointers represents a functional dependency between two software files, each of the plurality of dependency pointers having a dependency confidence factor being a function of the dependency between the two software files and a historical record of installations involving the dependency between the two software files.

12. The method of claim 11 wherein the dependency confidence factor represents an estimate that the dependency between the two software files is accurate.

13. The method of claim 1 further comprising:

obtaining a location pointer from each of the subset of software elements, the location pointer identifying a memory location of the software file associated with the corresponding software element.

14. The method of claim 13 further comprising:

obtaining each of the software files from the memory location of a relational database.

15. The method of claim 1 wherein each of the plurality of software files comprises one of the following types of software files:

a) an executable file;

b) a shared library file;

c) a configuration file; and

d) a script file.

16. The method of claim 1 wherein each of the plurality of dependency pointers is associated with at least one of the first and second software elements creating the dependency.

17. A method for installing software comprising:

transmitting a software installation request for installing a first software functionality from a client device;

receiving, at the client device, at least one installation route from a software installation map, the installation route identifying;

a plurality of software elements for installing the first software functionality, each software element having an associated software file;

an installation order for installing the software files;

a confidence factor associated with the installation route, the confidence factor representing an estimate of whether the installation route will provide for a successful installation;

receiving the software files for installing the first software functionality, the plurality of software files associated with the at least one installation route; and

installing the software files to obtain the first software functionality.

18. The method of claim 17 further comprising:

obtaining a first installation route including at least a first subset of the plurality of software elements to install the first software functionality;

a second installation route including at least a second subset of the plurality of software elements, the second subset differing from the first subset by at least one software element, the second subset of software elements to install the first software functionality; and

determining a preferred installation route between the first and second installation routes.

19. The method of claim 17 further comprising:

transmitting a success rate to the software installation map, wherein the success rate is a function of the success of installing the software functionality.

20. The method of claim 17 further comprising:

transmitting at least one installation criteria for installing the first software functionality, the at lest one installation criteria represent at least one of the following types of requirements for installing the first software functionality;

operating speed of the software functionality, stability of the software functionality, version of the software functionality, and compatibility of the software functionality with other software functionality.