Apparatus and method fro maintaining a software repository

• US 8,527,979 B2
• Filed: 06/16/2011
• Issued: 09/03/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/162,429
• Publication Number:
  US 20110246982A1
• Time in Patent Office: 810 Days
• Field of Search: 717/169
• US Class Current: 717/169
• 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 maintaining a software repository of software files used for installing at least a first software functionality comprising:

utilizing at least one processor to perform the operations of;

maintaining a first software application within a primary storage facility of the software repository, the first software application comprising a plurality of software files wherein each software file is represented by a plurality of software elements maintained in a software installation map,

wherein each software element maintained in the software installation map has at least one associated dependency on at least one other software element maintained in the software installation map and a confidence factor associated with the dependency, the confidence factor indicating at least a number of successful prior installations involving the dependency;

updating a usage factor of a first software element associated with a first software file from the plurality of software files, the usage factor being a function of a number of times the first software file is installed during a first time period and the confidence factor; and

moving the first software file from the primary storage facility of the software repository to a secondary storage facility as a function of the usage factor.

2. The method of claim 1 further comprising:

comparing the usage factor against a threshold value; and

moving the first software file from the primary storage facility of the software repository to a secondary storage facility if the usage factor meets the threshold value.

3. The method of claim 2 further comprising:

updating an aging value of the first software element as a function of the confidence factor associated with the dependency.

4. The method of claim 3 further comprising:

comparing the aging value to a second threshold; and

moving the first software file from the primary storage facility of the software repository to a secondary storage facility if the aging value meets the second threshold value.

5. The method of claim 3 further comprising:

updating the aging value of the first software element as function of the confidence factor associated with the dependency and the usage factor of the first software element; and

moving the first software file from the primary storage facility of the software repository to a secondary storage facility as a function of the aging factor.

6. The method of claim 2 wherein each software element maintained in the software installation map has a plurality of confidence factors associated with the dependency;

the method further comprising;

updating an aging value of the first software element as a function of the confidence factors associated with the dependency.

7. The method of claim 6 further comprising:

updating an aging value of the first software element as a function of an average of the confidence factors associated with the dependency.

8. The method of claim 7 further comprising:

comparing the aging value to a second threshold; and

moving the first software file from the primary storage facility of the software repository to a secondary storage facility if the aging value meets the second threshold value.

9. The method of claim 1 further comprising:

deleting the first software file from at least one of the primary storage facility and secondary storage facility as a function of the usage factor.

10. The method of claim 3 further comprising:

deleting the first software file from at least one of the primary storage facility and the secondary storage facility as a function of the aging factor.

11. The method of claim 9 further comprising removing the software element from the installation map.

12. A method for maintaining a software repository of software files used for installing at least a first software functionality comprising:

maintaining a first software application within a primary storage facility of the software repository, the first software application comprising a plurality of software files wherein each software file is represented by a plurality of software elements maintained in a software installation map, wherein each software element maintained in the software installation map has at least one associated dependency on at least one other software element maintained in the software installation map and a confidence factor associated with the dependency, the confidence factor indicating at least a number of successful prior installations involving the dependency;

updating, utilizing at least one processing device, an aging factor of a first software element associated with a first software file from the plurality of software files, the aging factor being a function of at least one of a number of times the first software file is installed during a first time period and the confidence factor; and

moving the first software file from the primary storage facility of the software repository to a secondary storage facility as a function of the aging factor.

13. The method of claim 12 further comprising:

comparing the aging factor against a threshold value; and

moving the first software file from the primary storage facility of the software repository to a secondary storage facility if the aging factor meets the threshold value.

14. The method of claim 12 further comprising:

deleting the first software file from the secondary storage facility when the first software element representing the first software file is not requested from the software installation map during a predetermined period of time after updating the aging factor.

15. The method of claim 12 further comprising:

deleting the first software element from the software installation map as a function of the aging factor.

16. The method of claim 15 further comprising:

maintaining a log of deleted software files.

17. The method of claim 12 wherein the primary storage facility is a relational database.

18. The method of claim 12 wherein the secondary storage facility is a tape drive system.

19. A system for maintaining a software warehouse of software files used for installing at least a first software functionality comprising:

a first non-transitory storage medium for hosting a plurality of software files wherein each of the plurality of software files are represented by a software element maintained on a software installation map, wherein each software element maintained in the software installation map has at least one associated dependency on at least one other software element maintained in the software installation map and a confidence factor associated with the dependency, the confidence factor indicating at least a number of successful prior installations involving the dependency;

an aging module configured to monitor the plurality of software files and age a software file as function of at least one of a number of times the first software file is installed during a first time period and the confidence factor; and

a second non-transitory storage medium in communication with the first storage medium, the second storage medium for receiving from the first storage medium and hosting a plurality of software files when the age of the software file meets a threshold.

20. The system of claim 19 wherein the first storage medium includes a high speed relational database and the second storage medium includes a tape drive system.