Multi-level patching operation

• US 7,934,211 B2
• Filed: 06/30/2005
• Issued: 04/26/2011
• Est. Priority Date: 06/30/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Ganguly, Shamik, Nguyen, PhiDien Ha, Saha, Debashis
• Primary Examiner(s): Sough; Hyung S
• Assistant Examiner(s): JORDAN, KIMBERLY L
• Application Number:
  US11/174,069
• Publication Number:
  US 20070006209A1
• Time in Patent Office: 2,126 Days
• Field of Search: None
• US Class Current: 717/168
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

Techniques for performing a multi-level patching operation are described. According to one such technique, before a particular patch is applied, the data containers that are targeted by the particular patch are identified. A determination is made as to whether any of these target data containers already has been targeted by any previously applied patch. A determination also is made as to whether any other data container that contains (immediately or otherwise) any of the target data containers already has been targeted by any previously applied patch. If any target data container or any other data container that contains a target data container already has been targeted by a previously applied patch, then the particular patch is not applied to the target data containers.

Claims

1. A method comprising:

identifying a hierarchical path to one or more target class files that are to be replaced by a particular patch of a plurality of patches;

wherein the hierarchical path identifies at least one archive file that is not to be replaced, as a whole, by the particular patch;

wherein said one or more target class files are, at a time that said identifying is performed, contained within the at least one archive file;

determining whether any patch in the plurality of patches, other than the particular patch, has already targeted and been applied to the at least one archive file; and

responsive to, at least, determining that no patch in the plurality of patches, other than the particular patch, has already targeted and been applied to the at least one archive file, applying the particular patch to the one or more target class files;

wherein the steps are performed by one or more computing devices.

2. The method of claim 1, further comprising:

responsive to determining that any patch in the plurality of patches, other than the particular patch, has already targeted and been applied to the at least one archive file, generating information that identifies one or more patches that already have been applied to the at least one archive file.

3. The method of claim 1, further comprising:

responsive to determining that any patch in the plurality of patches, other than the particular patch, has already targeted and been applied to the at least one archive file, generating information that identifies one or more archive files to which any patch other than the particular patch already has been applied.

4. The method of claim 1,

wherein the one or more target class files are a first set of one or more target class files;

wherein the at least one archive file is a first archive file residing at a first node of a multi-node system;

wherein the method further comprises;

identifying a second set of one or more target class files that will be replaced by the particular patch;

wherein said second set of one or more target class files is, at a time that said identifying the second set is performed, contained within a second archive file at a second node of the multi-node system; and

determining whether any patch in the plurality of patches, other than the particular patch, has already targeted and been applied to the second archive file;

wherein applying the particular patch to the first set of the one or more target class files is further performed responsive to at least determining that no patch in the plurality of patches, other than the particular patch, has already targeted and been applied to the second archive file;

wherein the first node is different than the second node.

5. The method of claim 1, wherein the at least one archive file is one of a Java archive file, web archive file, or enterprise archive file.

6. The method of claim 1, wherein the at least one archive file is a first archive file contained within a second archive file, the method further comprising:

determining whether any patch in the plurality of patches, other than the particular patch, has already targeted and been applied to the second archive file;

wherein applying the particular patch to the one or more target class files is further performed responsive to at least determining that no patch in the plurality of patches, other than the particular patch, already has targeted and been applied to the second archive file.

7. The method of claim 1, wherein applying the patch to the one or more target class files comprises:

expanding the at least one archive file into a directory structure;

patching the one or more target class files within the directory structure; and

collapsing the directory structure back into the at least one archive file.

8. The method of claim 1, wherein the at least one archive file contains one or more files in addition to the one or more target class files.

9. A volatile or non-volatile computer-readable medium storing instructions that, when executed by one or more computing devices, cause:

identifying a hierarchical path to one or more target class files that are to be replaced by a particular patch of a plurality of patches;

wherein the hierarchical path identifies at least one archive file that is not to be replaced, as a whole, by the particular patch;

wherein said one or more target class files are, at a time that said identifying is performed, contained within the at least one archive file;

determining whether any patch in the plurality of patches, other than the particular patch, has already targeted and been applied to the at least one archive file; and

responsive to, at least, determining that no patch in the plurality of patches, other than the particular patch, has already targeted and been applied to the at least one archive file, applying the particular patch to the one or more target class files.

10. The volatile or non-volatile computer-readable medium of claim 9, wherein the instructions, when executed by the one or more computing devices, further cause:

responsive to determining that any patch in the plurality of patches, other than the particular patch, has already targeted and been applied to the at least one archive file, generating information that identifies one or more patches that already have been applied to the at least one archive file.

11. The volatile or non-volatile computer-readable medium of claim 9, wherein the instructions, when executed by the one or more computing devices, further cause:

responsive to determining that any patch in the plurality of patches, other than the particular patch, has already targeted and been applied to the at least one archive file, generating information that identifies one or more archive files to which any patch other than the particular patch already has been applied.

12. The volatile or non-volatile computer-readable medium of claim 9,

wherein the one or more target class files are a first set of one or more target class files;

wherein the at least one archive file is a first archive file residing at a first node of a multi-node system;

wherein the instructions, when executed by the one or more computing devices, further cause;

identifying a second set of one or more target class files that will be replaced by the particular patch;

wherein said second set of one or more target class files is, at a time that said identifying the second set is performed, contained within a second archive file at a second node of the multi-node system;

determining whether any patch in the plurality of patches, other than the particular patch, has already targeted and been applied to the second archive file; and

wherein applying the particular patch to the first set of the one or more target class files is further performed responsive to at least determining that no patch in the plurality of patches, other than the particular patch, already has targeted and been applied to the second archive file

wherein the first node is different than the second node.

13. The volatile or non-volatile computer-readable medium of claim 9, wherein the at least one archive file is one of a Java archive file, web archive file, or enterprise archive file.

14. The volatile or non-volatile computer-readable medium of claim 9, wherein the at least one archive file is a first archive file contained within a second archive file, wherein the instructions, when executed by the one or more computing devices, further cause:

determining whether any patch in the plurality of patches, other than the particular patch, has already targeted and been applied to the second archive file;

wherein applying the particular patch to the one or more target class files is further performed responsive to at least determining that no patch in the plurality of patches, other than the particular patch, already has targeted and been applied to the second archive file.

15. The volatile or non-volatile computer-readable medium of claim 9, wherein applying the patch to the one or more target class files comprises:

expanding the at least one archive file into a directory structure;

patching the one or more target class files within the directory structure; and

collapsing the directory structure back into the at least one archive file.

16. The volatile or non-volatile computer-readable medium of claim 9, wherein the at least one archive file contains one or more files in addition to the one or more target class files.