System and method for software patching for cross-platform products

• US 7,735,078 B1
• Filed: 10/30/2003
• Issued: 06/08/2010
• Est. Priority Date: 10/30/2003
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Vaidya, Neelam N.
• Primary Examiner(s): Zhen; Wei Y
• Assistant Examiner(s): Wu; Junchun
• Application Number:
  US10/696,964
• Time in Patent Office: 2,413 Days
• Field of Search: 717168-173
• US Class Current: 717/171
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates
• CPC Class Codes: G06F 9/44547 Fat binaries

Abstract

A system and method for cross-platform patching of applications. The method may include deploying a patch package on a first computer running a first type of operating system, and executing the patching mechanism on the first computer. The patch package may include a patching mechanism operable to execute on a second computer running a second type of operating system. The patch package may also include a first set of one or more new code components, which may replace a first set of one or more old code components in a first application. The patch package may also be deployed on the second computer. The method may also include replacing a second set of one or more old code components in a second application on the second computer with a second set of one or more new code components included in the patch package.

Claims

1. A method for patching applications, comprising:

deploying a patch package on a first computer running a first type of operating system,

wherein the patch package comprises a patching mechanism and a first set of one or more new code components, and

wherein the patching mechanism is executable on the first computer running the first type of operating system to install the first set of one or more new code components and is also executable on a second computer running a second type of operating system to install one or more new code components;

wherein the patching mechanism and the first set of one or more new code components are deployed together on the first computer as part of the same patch package; and

executing the patching mechanism on the first computer,

wherein executing the patching mechanism comprises the patching mechanism performing a replacement of a first set of one or more old code components in a first application with the first set of one or more new code components.

2. The method of claim 1, further comprising:

deploying the patch package on the second computer,

wherein the patch package further comprises a second set of one or more new code components; and

executing the patching mechanism on the second computer,

wherein executing the patching mechanism comprises the patching mechanism replacing a second set of one or more old code components in a second application with the second set of one or more new code components,

wherein the second application is functionally equivalent to the first application.

3. The method of claim 1 wherein the patching mechanism is written in a cross-platform language.

4. The method of claim 1 wherein the patching mechanism is a script written in a cross-platform scripting language.

5. The method of claim 1, further comprising storing the first set of one or more old code components in a separate location before being replaced with the first set of one or more new code components.

6. The method of claim 5, further comprising restoring the first set of one or more old code components to the first application.

7. The method of claim 1 wherein the patch package further comprises a patch information file, wherein the patch information file comprises information on the first set of one or more new code components and information regarding which application the patch package is applicable to patch.

8. The method of claim 7, wherein the patch information file further comprises information on what bugs the patch package is operable to fix, and information regarding which other patch packages the patch package is incompatible with.

9. The method of claim 8, further comprising storing information on one or more other patch packages that have been previously applied to the first application in a package information file.

10. The method of claim 9, further comprising detecting patch conflicts by comparing the patch information file to the package information file.

11. The method of claim 1 wherein the user interface for the patching mechanism is the same on different platforms.

12. A system for patching applications, comprising:

a first computer comprising one or more processors configured during operation for running a first type of operating system;

a first application executable on the first computer,

wherein the first application comprises one or more old code components; and

a patch package comprising a patching mechanism and a first set of one or more new code components,

wherein the patching mechanism is executable on the first computer running the first type of operating system to install the first set of one or more new code components to replace the one or more old code components with the first set of one or more new code components, and

wherein the patching mechanism is also executable on a second computer running a second type of operating system to install one or more new code components;

wherein the patching mechanism and the first set of one or more new code components are deployed together on the first computer as part of the same patch package.

13. The system of claim 12, further comprising:

a second application executable on the second computer,

wherein the second application comprises a second set of one or more old code components, and

wherein the second application is functionally equivalent to the first application; and

a second set of new code components,

wherein the second set of new code components is stored in the patch package, and

wherein the patching mechanism is executable on the second computer to replace the second set of one or more old code components with the second set of one or more new code components.

14. The system of claim 12 wherein the patching mechanism is written in a cross-platform language.

15. The system of claim 12 wherein the patching mechanism is a script written in a cross-platform scripting language.

16. The system of claim 12 wherein the patching mechanism is further operable to store the first set of one or more old code components in a separate location before being replaced with the first set of one or more new code components.

17. The system of claim 16 wherein the patching mechanism is further operable to restore the first set of one or more old code components to the first application.

18. The system of claim 12 wherein the patch package further comprises a patch information file, wherein the patch information file comprises information on the first set one or more new code components and information regarding which application the patch package is applicable to patch.

19. The system of claim 18, wherein the patch information file further comprises information on what bugs the patch package is operable to fix, and information regarding which other patch packages the patch package is incompatible with.

20. The system of claim 19 wherein the patching mechanism is further operable to store information on one or more other patch packages that have been previously applied to the first application in a package information file.

21. The system of claim 20 wherein the patching mechanism is further operable to detect patch conflicts by comparing the patch information file to the package information file.

22. The system of claim 12 wherein the user interface for the patching mechanism is identical on different platforms.