Systems and methods for updating multi-tier cloud-based application stacks

Patent metadata

Field	Value
Publication number	US-10732964-B2
Application number	US-201816137845-A
Country	US
Kind code	B2
Filing date	Sep 21, 2018
Priority date	Sep 21, 2017
Publication date	Aug 4, 2020
Grant date	Aug 4, 2020

Abstract

The present disclosure relates to automatically and periodically updating a multi-tier application stack in a cloud environment. More particularly, the present disclosure relates to systems and methods that access a central server to determine if new updates have been released, and when new updates have been released, automatically apply the new updates to an application environment with minimal network burden and service interruption.

First claim

What is claimed is:

1. A computer-implemented method, comprising:
running an instance of an application environment in a production environment, wherein the application environment includes a plurality of components, and wherein each component of the plurality of components includes one or more objects;
detecting one or more updates configured to modify at least one object of a component of the plurality of components;
in response to detecting the one or more updates, accessing an update server to retrieve the one or more updates;
automatically generating a new instance of the application environment;
installing the one or more updates on the new instance of the application environment;
identifying metadata associated with the instance, the metadata characterizing each object of the one or more objects of each component of the plurality of components associated with the instance;
identifying new metadata associated with the new instance, the new metadata characterizing each object of the one or more objects of each component of the plurality of components associated with the new instance, and the new metadata characterizing a version of the at least one object of the component having been updated with the one or more updates;
comparing the metadata associated with the instance with the new metadata associated with the new instance, wherein the comparison is performed while the instance of the application environment is running in the production environment;
determining, based on a result of the comparison, one or more differences between the metadata associated with the instance with the new metadata associated with the new instance, wherein the one or more differences identifies the at least one object of the component that has been updated based on the one or more updates;
generating update data that includes each of the one or more identified differences; and
updating the instance of the application environment using the update data by incorporating the one or more identified differences into the instance, wherein updating the instance includes modifying the at least one object identified by the one or more differences, and wherein the at least one identified object is updated based on the new metadata.

2. The computer-implemented method of claim 1 , wherein updating the instance further comprises:
initiating a lock period during which all transactions associated with an application running in the application environment are stopped;
updating the instance with the update data during the lock period; and
releasing the lock period, the release of the lock period enabling transactions associated with the application to continue.

3. The computer-implemented method of claim 1 , wherein the metadata includes a first set of bug numbers associated with the instance, wherein the new metadata includes a second set of bug numbers associated with the new instance, wherein when the first set of bug numbers is different from the second set of bug numbers, a difference between the first set and the second set corresponds to one or more bug fixes included in the one or more updates.

4. The computer-implemented method of claim 3 , wherein the at least one object having been updated based on the new metadata is associated with the one or more bug fixes included in the one or more updates.

5. The computer-implemented method of claim 1 , wherein detecting the one or more updates stored on a central server includes periodically polling the central server for updates at a regular or irregular interval.

6. The computer-implemented method of claim 1 , wherein the metadata is associated with source code without the one or more updates, and wherein the new metadata is associated with the source code with the one or more updates.

7. The computer-implemented method of claim 1 , further comprising:
rebooting the updated instance.

8. A system, comprising:
one or more processors; and
a non-transitory computer-readable storage medium containing instructions configured to cause the one or more processors to perform operations including:
running an instance of an application environment in a production environment, wherein the application environment includes a plurality of components, and wherein each component of the plurality of components includes one or more objects;
detecting one or more updates configured to modify at least one object of a component of the plurality of components;
in response to detecting the one or more updates, accessing an update server to retrieve the one or more updates;
automatically generating a new instance of the application environment;
installing the one or more updates on the new instance of the application environment;
identifying metadata associated with the instance, the metadata characterizing each object of the one or more objects of each component of the plurality of components associated with the instance;
identifying new metadata associated with the new instance, the new metadata characterizing each object of the one or more objects of each component of the plurality of components associated with the new instance, and the new metadata characterizing a version of the at least one object of the component having been updated with the one or more updates;
comparing the metadata associated with the instance with the new metadata associated with the new instance, wherein the comparison is performed while the instance of the application environment is running in the production environment;
determining, based on a result of the comparison, one or more differences between the metadata associated with the instance with the new metadata associated with the new instance, wherein the one or more differences identifies the at least one object of the component that has been updated based on the one or more updates;
generating update data that includes each of the one or more identified differences; and
updating the instance of the application environment using the update data by incorporating the one or more identified differences into the instance, wherein updating the instance includes modifying the at least one object identified by the one or more differences, and wherein the at least one identified object is updated based on the new metadata.

9. The system of claim 8 , wherein updating the instance further comprises:
initiating a lock period during which all transactions associated with an application running in the application environment are stopped;
updating the instance with the update data during the lock period; and
releasing the lock period, the release of the lock period enabling transactions associated with the application to continue.

10. The system of claim 8 , wherein the metadata includes a first set of bug numbers associated with the instance, wherein the new metadata includes a second set of bug numbers associated with the new instance, wherein when first set of bug numbers is different from the second set of bug numbers, a difference between the first set and the second set corresponds to one or more bug fixes included in the one or more updates.

11. The system of claim 10 , wherein the at least one object having been updated based on the new metadata is associated with the one or more bug fixes included in the one or more updates.

12. The system of claim 8 , wherein detecting the one or more updates stored on a central server includes periodically polling the central server for updates at a regular or irregular interval.

13. The system of claim 8 , wherein the metadata is associated with source code without the one or more updates, and wherein the new metadata is associated with the source code with the

Assignees

• Oracle Int Corp

Inventors

• Krishnappa Nagendra
• Narayanan Biju
• Sujatha Aneesh Azhakesan
• Chatim Aldoncar Milind Xete
• Narayanan Deepankar

Classifications

• G06F16/907

  Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually · CPC title

• G06F8/658 Primary

  Incremental updates; Differential updates · CPC title

• G06F8/656

  while running · CPC title

• G06F9/4401

  Bootstrapping (security arrangements therefor G06F21/57) · CPC title