Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:14
From version 12.1
edited by Erik Bakker
on 2024/06/24 14:05
Change comment: There is no comment for this version
To version 13.1
edited by Erik Bakker
on 2024/06/24 14:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,7 +17,7 @@
17 17  
18 18  In essence any container image consists of three layers. The first (foundational) layer comprises of a wide array of open source code heavenly rooted in the Spring and Java frameworks. The secondary layer consist of your collection of flows that should run on a container (i.e runtime). This layer is built up by the various flow designer components that are used in the flow versions in your release. The third layer is the configuration layer in the form of (application) properties, memory configuration, and other configuration elements (i.e. route, deployment location, volumes, runtime settings). Below you see a picture that illustrates this concept in an abstract form. In eMagiz, as well as in the image, you see that the three layers form one construct that facilitates the purpose of the object. For eMagiz is that the handling of data via integrations.
19 19  
20 -[[image:Main.Images.Microlearning.WebHome@advanced-lifecycle-management-impact-of-runtime-image-upgrades--runtime-layers.jpeg]]
20 +[[image:Main.Images.Microlearning.WebHome@advanced-lifecycle-management-impact-of-runtime-image-upgrades--runtime-layers.png]]
21 21  
22 22  === 3.1 Overal deployment strategy ===
23 23