Changes for page Impact of Runtime Image Upgrades
Last modified by Erik Bakker on 2024/09/03 08:14
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -6,16 +6,18 @@ 6 6 == 1. Prerequisites == 7 7 8 8 * Advanced knowledge of the eMagiz platform 9 -* Complete the microlearning that explains how to upgrade to a new buildnumber 10 10 11 11 == 2. Key concepts == 11 + 12 +With runtime image we mean the template that is used when creating runtime specific images. That image is used to spin up docker containers and contains all required software components to let the docker container function properly. One of the key requirements is to load the required libraries that are used by flows that are part of that runtime. 12 12 13 - Withbuildnumberswe mean the piece ofsoftware that used by a flow to make it operational inside the runtime. Several eMagizlibraries are loadedtogetherwith the flow componentsXML intotheruntime(Java container). In essence thatmeans that a new buildnumber means the flow is technically speakingdifferent from the previousbuildnumber.14 +== 3. Assessing the impact of runtime images == 14 14 15 -eMagiz works hard to limit the number of buildnumbers. The general approach for buildnumber is that these are backwards compatible, so the impact of moving to the next buildnumber poses a minimal impact and risk. 16 - 17 -== 3. Assessing the impact of changing buildnumbers == 18 - 16 +As mentioned the runtime image is a template which effectively means that all specific images that are created 17 + 18 + 19 + 20 + 19 19 === 3.1 Release notes & impact assessment === 20 20 21 21 These can be found [[here>>doc:Main.Release Information.Build numbers.WebHome||target="blank"]]. Once the release notes are properly read, assess the impact. This effectively means that the key notes around the model components can be used.