Apparatus and method for automated software installation

• US 8,533,704 B2
• Filed: 06/02/2011
• Issued: 09/10/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): DENG, ANNA CHEN
• Application Number:
  US13/152,088
• Publication Number:
  US 20110239212A1
• Time in Patent Office: 831 Days
• Field of Search: 717168-178
• US Class Current: 717/174
• 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 automating software installations accounting for an installation policy, the method comprising:

defining a client installation policy for a client device, wherein the client installation policy defines a level of manual interaction suggested for installing software functionalities on the client device;

transmitting a software installation request for installing a first software functionality;

receiving, at a service provider, a software installation route from a software installation map, the software installation route describes a plurality of software files for installing the first software functionality, and a plurality of dependency pointers representing dependencies between each of the plurality of software files for installing the first software functionality, the software installation route comprising;

a confidence factor representing an indication of previous installation success based on the software installation route;

a route installation policy defines a level of manual interaction suggested for installing the first software functionality, wherein the route installation policy is a function of the confidence factor associated with the software installation route; and

installing the first software functionality at the client device based on a combination of the client installation policy and the route installation policy.

2. The method of claim 1 further comprising:

overriding the route installation policy to install the first software functionality based on the client installation policy.

3. The method of claim 1 further comprising:

overriding the client installation policy to install the first software functionality based on the route installation policy.

4. The method of claim 1 wherein the route installation policy is a function of the confidence factor associated with the software installation route.

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

a plurality of software elements representing a plurality of software files; and

a plurality of dependency pointers representing dependencies between each of the plurality of software files.

6. The method of claim 1 wherein the client installation policy automatically changes over time based on a historical record of successful installations performed on the client device.

7. The method of claim 6 wherein the client installation policy changes to suggest less manual interaction if the first software functionality installs successfully.

8. The method of claim 6 wherein the client installation policy changes to suggest more manual interaction if the first software functionality installs unsuccessfully.

9. A method for providing a software installation comprising:

maintaining, at a service provider, a software installation map comprising;

a plurality of software elements representing a plurality of software files;

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

a software installation route for installing a first software functionality, the software installation route including a subset of the plurality of software elements and a subset of the plurality dependency pointers for installing the first software functionality, a confidence factor representing an estimate of whether the software installation route will provide for a successful installation based on previous installation success of the software installation route, and a route installation policy defining a level of manual interaction suggested for installing the first software functionality;

receiving a request for installing the first software functionality from a client device; and

providing the software installation route to the client device.

10. The method of claim 9 wherein the route installation policy is a function of the confidence factor.

11. The method of claim 10 further comprising:

receiving an indication of success from the installation of the first software functionality, wherein the indication of success describes whether the installation resulted in one or more errors.

12. The method of claim 11 further comprising:

altering the route installation policy based on the indication of success.

13. The method of claim 12 wherein the operation of altering the route installation policy increases a suggested level of manual interaction if the indication of success returned one or more installation errors.

14. The method of claim 12 wherein the operation of altering the route installation policy decreases the suggested level of manual interaction if the indication of success returned no installation errors.

15. The method of claim 9 wherein the route installation policy suggests a decreased level of manual interaction if the confidence factor of the software installation route is increased.

16. The method of claim 9 wherein the route installation policy suggests a increased level of manual interaction if the confidence factor of the software installation route is reduced.

17. The method of claim 10 wherein the route installation policy is a function of a number of installations performed based on the first software installation route.