Patch management system

• US 8,245,216 B2
• Filed: 10/06/2006
• Issued: 08/14/2012
• Est. Priority Date: 10/11/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Felts, David
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Smith, Cheneca
• Application Number:
  US11/539,261
• Publication Number:
  US 20070113225A1
• Time in Patent Office: 2,139 Days
• Field of Search: None
• US Class Current: 717/169
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

Patch management system can be used for maintaining patches downloaded for software. The patch management system can ensure that there are no conflicts between the installed patches.

Claims

1. A method of managing and applying patches for software programs, comprising the steps of:

providing at a computer, including a processor and memory, a central patch management system which includes a global patch depository that stores available patches or patch information, for application to software programs running on local machines, wherein each particular patch or patch information in the global patch depository has associated therewith

a metadata that is used to determine relationships and dependencies with other patches, including

information describing how the particular patch or patch information is to be applied with respect to previously installed patches, and

information describing how the patch can be rolled back, and

a scope information that indicates how the patch is scoped;

providing at one or more local machines which includes one or more installed software programs, a local patch management system which includes

a local patch depository, that is used to store selected patches or patch information from the global patch depository, and apply the selected patches or patch information for the one or more installed software programs on that local machine, and

a maintenance archive which maintains indications of files and classes from previously-applied patches to enable rollback; and

using the metadata and the scope information associated with each patch or patch information, including the relationships and dependencies determined thereby, to control the packaging and application of the selected patches or patch information to the software programs at the local machines, in accordance with their scope, including during installation of a particular patch injecting that patch into the archive and storing backup files as necessary to enable rollback.

2. The method of claim 1, wherein each local patch management on a particular local machine can support multiple domains operating on that local machine, for running the one or more installed software programs therein, and wherein each domain operating on that local machine includes its own patch configuration, and wherein at least some of the patches are domain-scoped so that the system can be used to patch each domain'"'"'s patch configuration independently of one another.

3. The method of claim 2, wherein a first domain and its own patch configuration is used as a test environment for the software program, and wherein a second domain and its own patch configuration is used as a production environment for the software program, and wherein the domain-scoped patches can be independently applied to either, or both domains.

4. The method of claim 1, wherein the patch management system maintains the patch configurations for multiple software programs.

5. The method of claim 1, wherein the software program is an application server program.

6. The method of claim 1, wherein the patch management system keeps track of files and class paths modified, during application of any patch, and allows the rollback of a patch without requiring the software program to be reinstalled.

7. A system for use in managing and applying patches for software programs, comprising:

a computer, including a processor and memory, wherein the computer further includes

a central patch management system which includes a global patch depository that stores available patches or patch information, for application to software programs running on local machines, and

wherein each particular patch or patch information in the global patch depository has associated therewith

a metadata that is used to determine relationships and dependencies with other patches, including

information describing how the particular patch or patch information is to be applied with respect to previously installed patches, and

information describing how the patch can be rolled back, and

a scope information that indicates how the patch is scoped;

one or more local machines, wherein each local machine includes

one or more installed software programs, and

a local patch management system which includes

a local patch depository, that is used to store selected patches or patch information retrieved from the global patch depository, and apply the selected patches or patch information for the one or more installed software programs on that local machine, and

a maintenance archive which maintains indications of files and classes from previously-applied patches to enable rollback; and

wherein the system uses the metadata and the scope information associated with each patch or patch information, including the relationships and dependencies determined thereby, to control the packaging and application of the selected patches or patch information to the software programs at the local machines, in accordance with their scope, including during installation of a particular patch injecting that patch into the archive and storing backup files as necessary to enable rollback.

8. The patch management system of claim 7, wherein each local patch management on a particular local machine can support multiple domains operating on that local machine, for running the one or more installed software programs therein, and wherein each domain operating on that local machine includes its own patch configuration, and wherein at least some of the patches are domain-scoped so that the system can be used to patch each domain'"'"'s patch configuration independently of one another.

9. The patch management system of claim 8, wherein a first domain and its own patch configuration is used as a test environment for the software program, and wherein a second domain and its own patch configuration is used as a production environment for the software program, and wherein the domain-scoped patches can be independently applied to either, or both domains.

10. The patch management system of claim 7, wherein the patch management system maintains the patch configurations for multiple software programs.

11. The patch management system of claim 7, wherein the software program is an application server program.

12. The patch management system of claim 7, wherein the local patch management system includes a graphical interface, that allows a user at a local machine to select the patches to be applied to the software programs at that location machine.

13. The patch management system of claim 12, wherein the graphical interface is adapted to show the applied patches.

14. The patch management system of claim 12, wherein the graphical interface is adapted to show available patches.

15. The patch management system of claim 7, wherein the patch management system keeps track of files and class paths modified, during application of any patch, and allows the rollback of a patch without requiring the software program to be reinstalled.

16. The patch management system of claim 7, wherein the patch management system allows for the installation of service packs.

17. The patch management system of claim 16, wherein the patches depend on a service pack such that the installation of a new service pack removes the patches.

18. The patch management system of claim 7, wherein the patch management system performs dependency checking using the metadata to determine whether a patch to be applied conflicts with a previously applied patch.

19. The patch management system of claim 7 wherein the local patch management system can connect to a server using the Internet to obtain patches from the global patch depository at the server.

20. A non-transitory computer readable storage medium, including instructions stored thereon, which when read and executed by one or more computers, cause the one or more computers to perform the steps comprising:

providing at a computer, including a processor and memory, a central patch management system which includes a global patch depository that stores available patches or patch information, for application to software programs running on local machines, wherein each particular patch or patch information in the global patch depository has associated therewith

a metadata that is used to determine relationships and dependencies with other patches, including

information describing how the particular patch or patch information is to be applied with respect to previously installed patches, and

information describing how the patch can be rolled back, and

a scope information that indicates how the patch is scoped;

providing at one or more local machines which includes one or more installed software programs, a local patch management system which includes

a local patch depository, that is used to store selected patches or patch information from the global patch depository, and apply the selected patches or patch information for the one or more installed software programs on that local machine, and

a maintenance archive which maintains indications of files and classes from previously-applied patches to enable rollback; and

using the metadata and the scope information associated with each patch or patch information, including the relationships and dependencies determined thereby, to control the packaging and application of the selected patches or patch information to the software programs at the local machines, in accordance with their scope, including during installation of a particular patch injecting that patch into the archive and storing backup files as necessary to enable rollback.