REDUCING DOWNTIME WHEN PATCHING MULTIPLE INTER-DEPENDENT SOFTWARE COMPONENTS
First Claim
Patent Images
1. A computing system comprising:
- a set of systems to store a plurality of software components implementing an enterprise application, wherein said plurality of software components are inter-dependent on each other according to a dependency order;
a developer system to send a plurality of patches sought to be applied to said plurality of software components; and
a patch tool to apply said plurality of patches on respective software components after all of said plurality of software components are in a shutdown state,said patch tool to start up said plurality of software components in said dependency order starting first with an independent component, wherein said independent component is contained in said plurality of software components.
1 Assignment
0 Petitions
Accused Products
Abstract
According to an aspect of the present invention, the dependency information of software components implementing an enterprise application, is used to minimize the down time of the components when applying patches. In an embodiment, all the software components are shut down before applying patches. The patches are then applied and the components are started in a dependency order starting from an independent component. The down time is reduced as a result. According to another aspect, the shutdown also is performed in the reverse of the dependency order. The shutdown and starting are performed using recursive logic.
-
Citations
20 Claims
-
1. A computing system comprising:
-
a set of systems to store a plurality of software components implementing an enterprise application, wherein said plurality of software components are inter-dependent on each other according to a dependency order; a developer system to send a plurality of patches sought to be applied to said plurality of software components; and a patch tool to apply said plurality of patches on respective software components after all of said plurality of software components are in a shutdown state, said patch tool to start up said plurality of software components in said dependency order starting first with an independent component, wherein said independent component is contained in said plurality of software components. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A machine readable medium carrying one or more sequences of instructions for causing a system to facilitate applying of patches to a plurality of software components implementing an enterprise application, said plurality of software components being inter-dependent on each other, wherein execution of said one or more sequences of instructions by one or more processors contained in said system causes said system to perform the actions of:
-
receiving a plurality of patches that are sought to be applied to said plurality of software components; forming a metadata corresponding to each of said plurality of software components, wherein the metadata corresponding to a software component indicates the specific ones of said plurality of software components that are dependent on the software component; including the metadata corresponding to the software component and a set of patches sought to be applied to the software component in a component package, the set of patches being contained in said plurality of patches; and generating a deployment package containing the component packages corresponding to the plurality of software components for deployment. - View Dependent Claims (10, 11, 12, 13)
-
-
14. A method of applying patches to a plurality of software components implementing an enterprise application, said plurality of software components being inter-dependent on each other according to a dependency order, said method comprising:
-
receiving a plurality of patches sought to be applied on said plurality of software components; shutting down said plurality of software components executing on a set of systems; applying said plurality of patches to said plurality of software components; and starting said plurality of software components in said dependency order starting with an independent component comprised in said plurality of software components. - View Dependent Claims (15, 16, 17, 18, 19, 20)
-
Specification