Reducing downtime when patching multiple inter-dependent software components

• US 9,195,455 B2
• Filed: 04/01/2009
• Issued: 11/24/2015
• Est. Priority Date: 04/01/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Sriram, Vijay Nichinbatl, Ganguly, Shamik, Sah, Rohit, Mukherjee, Sourav
• Primary Examiner(s): Do, Chat
• Assistant Examiner(s): CURBELO III, SERGIO JOSE
• Application Number:
  US12/416,151
• Publication Number:
  US 20100257517A1
• Time in Patent Office: 2,428 Days
• Field of Search: 717110-113, 717/168, 340 11- 161, 375354-376, 713 1- 2, 713/100
• US Class Current: 1/1
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates

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.

Claims

1. A computing system comprising:

a set of systems to store a plurality of software components implementing an enterprise application containing a plurality of layers, wherein software components in each layer are designed to provide services to software components in higher layers while using services provided by software components in lower layers, wherein said plurality of software components are inter-dependent on each other according to a dependency order, wherein a first software component is dependent on a second software component, which in turn is dependent on a third software component according to said dependency order, a fourth software component is also dependent on said third software component without being dependent on said second software component, wherein said first software component and said fourth software component are present in a third layer, said second software component is present in a second layer and said third software component is present in a first layer, wherein said third layer is higher than said second layer, which in turn is higher than said first layer in said plurality of layers, wherein each software component in the same layer provides same services to components in higher layers such that both of said first software component and said fourth software component in said third layer provide same services to software components in a fourth layer which is higher than said third layer in said plurality of layers, wherein said first software component, said second software component, said fourth software component and said third software component are contained in said plurality of software components;

a developer system to send a plurality of patches sought to be applied to said plurality of software components, wherein said plurality of patches includes respective patches for said first software component, said second software component and said third software component;

and a patch tool to apply said plurality of patches on respective software components after all of said plurality of software components, including said first software component, said second software component, said third software component and said fourth software component 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, wherein said patch tool starts up each component after completion of patching of the component and after starting up of a set of components on which the component is dependent upon, without waiting for patching of all of said plurality of software components, wherein each software component continues to be in executing state after being started up until all of said plurality of software components are also started up, wherein services provided by the software component in the executing state are available to corresponding components in higher layers, wherein said third software component is started up at a third time instance after completion of patching of said third software component, but without waiting for completion of patching of said second software component and said first software component in view of said second layer being higher than said first layer, wherein said second software component is started up at a second time instance after completion of patching of said second software component, but without waiting for completion of patching of said first software component in view of said third layer being higher than said second layer, wherein said first software component is started up at a first time instance after completion of patching of said first software component and said starting up of said second software component, wherein said fourth software component in said third layer is started up at a fourth time instance after completion of patching of said fourth software component and said starting up of said third software component in said first layer, but without waiting for said starting up of said second component in said second layer in view of said fourth software component not being dependent on said second software component, wherein said first time instance is after said second time instance, which in turn is after said third time instance, and wherein said fourth time instance is after said third time instance but before said second time instance, wherein at least one of said set of systems, said developer system and said patch tool comprising a processor executing instructions retrieved from a memory.

2. The computing system of claim 1, wherein said dependency order is represented by a dependency data, wherein said patch tool examines said dependency data to determine said dependency order.

3. The computing system of claim 2, wherein said dependency data comprises a plurality of metadata, each metadata being included associated with a respective component, the metadata associated with a component indicating a set of components which are dependent on the component, each of said plurality of software components being associated with a corresponding one of a plurality of deployment logics, said patch tool being operable to first send a shutdown command to the deployment logic associated with said independent component, wherein the deployment logic of each of said plurality of software components, including said independent component, is designed to send a shutdown request to the deployment logics of dependent components indicated by corresponding one of said plurality of metadata and is designed to shutdown the associated software component after receiving an indication that corresponding dependent components are shutdown, whereby shutdown happens in a reverse dependency order ending with said independent component, said patch tool being operable to then send a patch and startup command to the deployment logic associated with said independent component, wherein the deployment logic of each of said plurality of software components, including said independent component, is designed to first apply to applicable ones of said plurality of patches to the associated software component, then startup the associated software component and then send another indication to the deployment logics of the dependent components according to the associated metadata, whereby said plurality of software components are started in said dependency order starting with said independent component.

4. The computing system of claim 3, wherein said indications for shutdown of the dependent components of a component are sent in parallel.

5. The computing system of claim 4, wherein said indications for patch and startup of the dependent components of a component are also sent in parallel.

6. The computing system of claim 2, wherein said dependency data is formed in said patch tool.

7. The computing system of claim 2, wherein said dependency data is formed in said developer system and sent to said patch tool along with said plurality of patches in the form a deployment package.

8. The computing system of claim 1, wherein said plurality of software components comprise a database system, a cluster ready service, an automated storage management and an application server software.

9. The computing system of claim 1, wherein said first software component and said fourth software component are different execution instances of a same software program providing same services to software components in said fourth layer, wherein said fourth layer contains a fifth software component which is dependent on said fourth software component, without being dependent on said first software component, wherein said fifth software component is started up after said starting up of said fourth software component, but without waiting for said starting up of said first software component.

10. A method of applying patches to a plurality of software components implementing an enterprise application containing a plurality of layers, wherein software components in each layer are designed to provide services to software components in higher layers while using services provided by software components in lower layers, said plurality of software components including a first software component, a second software component, a third software component and a fourth software component, wherein said first software component and said fourth software component are present in a third layer, said second software component is present in an second layer and said third software component is present in a first layer, wherein said third layer is higher than said second layer, which in turn is higher than said first layer in said plurality of layers, wherein each software component in the same layer provides same services to components in higher layers such that both of said first software component and said fourth software component in said third layer provide same services to software components in a fourth layer which is higher than said third layer in said plurality of layers, said method comprising:

receiving a dependency data associated with a plurality of patches sought to be applied on said plurality of software components, said dependency data indicating inter-dependencies among said plurality of software components, wherein said plurality of patches includes respective patches for said first software component, said second software component and said third software component;

shutting down said plurality of software components, including said first software component, said second software component, said third software component and said fourth software component, executing on a set of systems;

examining said dependency data to determine a dependency order among said plurality of software components, wherein said dependency order indicates, for each component, a corresponding set of components that are dependent on the component, wherein said dependency order indicates that said first software component is dependent on said second software component, that said second software component is in turn dependent on said third software component, and that a fourth software component is also dependent on said third software component without being dependent on said second software component;

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, wherein said starting starts up each component after completion of patching of the component and after starting up of a set of components on which the component is dependent upon, without waiting for patching of all of said plurality of software components, wherein said third software component is started up at a third time instance after completion of patching of said third software component, but without waiting for completion of patching of said second software component and said first software component in view of said second layer being higher than said first layer, wherein said second software component is started up at a second time instance after completion of patching of said second software component, but without waiting for completion of patching of said first software component in view of said third layer being higher than said second layer, wherein said first software component is started up at a first time instance after completion of patching of said first software component and said starting up of said second software component, wherein said fourth software component in said third layer is started up at a fourth time instance after completion of patching of said fourth software component and starting up of said third software component in said first layer, but without waiting for said starting up of said second component in said second layer in view of said fourth software component not being dependent on said second software component, wherein said first time instance is after said second time instance, which in turn is after said third time instance, and wherein said fourth time instance is after said third time instance but before said second time instance.

11. The method of claim 10, wherein said plurality of software components are also shutdown in said dependency order determined based on said dependency data.

12. The method of claim 11, wherein said shutting down and starting are performed using a recursive logic implemented associated with each of said plurality of software components.

13. The method of claim 12, wherein said dependency data comprises a plurality of metadata, each metadata being included associated with a respective component, the metadata associated with a component indicating a set of components which are dependent on the component, each of said plurality of software components being associated with a corresponding one of a plurality of deployment logics, said method comprising:

sending a shutdown command to the deployment logic associated with said independent component, wherein the deployment logic of each of said plurality of software components, including said independent component, is designed to send a shutdown request to the deployment logics of dependent components indicated by corresponding one of said plurality of metadata and is designed to shutdown the associated software component after receiving an indication that corresponding dependent components are shutdown, whereby shutdown happens in a reverse dependency order ending with said independent component,

and sending a patch and startup command to the deployment logic associated with said independent component after completion of shutdown of all of said plurality of software components,

wherein the deployment logic of each of said plurality of software components, including said independent component, is designed to first apply to applicable ones of said plurality of patches to the associated software component, then startup the associated software component and then send another indication to the deployment logics of the dependent components according to the associated metadata, whereby said plurality of software components are started in said dependency order starting with said independent component.

14. The method of claim 13, wherein said indications for shutdown of the dependent components of a component are sent in parallel.

15. The method of claim 13, wherein said indications for patch and startup of the dependent components of a component are also sent in parallel.

16. The method of claim 10, wherein said first software component and said fourth software component are different execution instances of a same software program providing same services to software components in said fourth layer, wherein said fourth layer contains a fifth software component which is dependent on said fourth software component, without being dependent on said first software component, wherein said fifth software component is started up after said starting up of said fourth software component, but without waiting for said starting up of said first software component.

17. A non-transitory machine readable medium storing 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 containing a plurality of layers, wherein software components in each layer are designed to provide services to software components in higher layers while using services provided by software components in lower layers, wherein said plurality of software components are inter-dependent on each other according to a dependency order, wherein a first software component is dependent on a second software component, which in turn is dependent on a third software component according to said dependency order, a fourth software component is also dependent on said third software component without being dependent on said second software component, wherein said first software component and said fourth software component are present in a third layer, said second software component is present in a second layer and said third software component is present in a first layer, wherein said third layer is higher than said second layer, which in turn is higher than said first layer in said plurality of layers, wherein each software component in the same layer provides same services to components in higher layers such that both of said first software component and said fourth software component in said third layer provide same services to software components in a fourth layer which is higher than said third layer in said plurality of layers, 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 dependency data associated with a plurality of patches sought to be applied on said plurality of software components, said dependency data indicating inter-dependencies among said plurality of software components, wherein said plurality of patches includes respective patches for said first software component, said second software component and said third software component;

shutting down said plurality of software components, including said first software component, said second software component, said third software component and said fourth software component, executing on a set of systems;

examining said dependency data to determine a dependency order among said plurality of software components, wherein said dependency order indicates, for each component, a corresponding set of components that are dependent on the component, wherein said dependency order indicates that said first software component is dependent on said second software component, that said second software component is in turn dependent on said third software component, and that a fourth software component is also dependent on said third software component without being dependent on said second software component;

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, wherein said starting starts up each component after completion of patching of the component and after starting up of a set of components on which the component is dependent upon, without waiting for patching of all of said plurality of software components, wherein said third software component is started up at a third time instance after completion of patching of said third software component, but without waiting for completion of patching of said second software component and said first software component in view of said second layer being higher than said first layer, wherein said second software component is started up at a second time instance after completion of patching of said second software component, but without waiting for completion of patching of said first software component in view of said third layer being higher than said second layer, wherein said first software component is started up at a first time instance after completion of patching of said first software component and said starting up of said second software component, wherein said fourth software component in said third layer is started up at a fourth time instance after completion of patching of said fourth software component and starting up of said third software component in said first layer, but without waiting for said starting up of said second component in said second layer in view of said fourth software component not being dependent on said second software component, wherein said first time instance is after said second time instance, which in turn is after said third time instance, and wherein said fourth time instance is after said third time instance but before said second time instance.

18. The non-transitory machine readable medium of claim 17, wherein said plurality of software components are also shutdown in said dependency order determined based on said dependency data.

19. The non-transitory machine readable medium of claim 18, wherein said shutting down and starting are performed using a recursive logic implemented associated with each of said plurality of software components.

20. The non-transitory machine readable medium of claim 19, wherein said dependency data comprises a plurality of metadata, each metadata being included associated with a respective component, the metadata associated with a component indicating a set of components which are dependent on the component, each of said plurality of software components being associated with a corresponding one of a plurality of deployment logics, said sequence of instructions further for:

sending a shutdown command to the deployment logic associated with said independent component, wherein the deployment logic of each of said plurality of software components, including said independent component, is designed to send a shutdown request to the deployment logics of dependent components indicated by corresponding one of said plurality of metadata and is designed to shutdown the associated software component after receiving an indication that corresponding dependent components are shutdown, whereby shutdown happens in a reverse dependency order ending with said independent component,

and sending a patch and startup command to the deployment logic associated with said independent component after completion of shutdown of all of said plurality of software components,

wherein the deployment logic of each of said plurality of software components, including said independent component, is designed to first apply to applicable ones of said plurality of patches to the associated software component, then startup the associated software component and then send another indication to the deployment logics of the dependent components according to the associated metadata, whereby said plurality of software components are started in said dependency order starting with said independent component.

21. The non-transitory machine readable medium of claim 17, wherein said first software component and said fourth software component are different execution instances of a same software program providing same services to software components in said fourth layer, wherein said fourth layer contains a fifth software component which is dependent on said fourth software component, without being dependent on said first software component, wherein said fifth software component is started up after said starting up of said fourth software component, but without waiting for said starting up of said first software component.