Skip to Content
Last modified by Erik Bakker on 2024/09/03 08:14
From version 1.1
edited by eMagiz
on 2022/11/21 15:46
Change comment: There is no comment for this version
To version 3.1
edited by eMagiz
on 2022/11/22 09:23
Change comment: There is no comment for this version

Summary

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 to create 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 of a runtime. A library in this context is a software component that performs a specific, often technical function in the eMagiz runtime. These libraries are Java based and different versions exist of these libraries.
12 12  
13 -With buildnumbers we mean the piece of software that used by a flow to make it operational inside the runtime. Several eMagiz libraries are loaded together with the flow components XML into the runtime (Java container). In essence that means that a new buildnumber means the flow is technically speaking different from the previous buildnumber.
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 from this template. The template holds all latest software updates and libraries that the integration flows require. eMagiz follows the strategy to update these required libraries on a frequent basis to ensure vulnerabilities can be fixed quickly and new functionality is available on a needed basis. Furthermore, by having a single template available all runtime are operating on exactly the same software base across all eMagiz clients. This way, a single mix of libraries can be made available to the community that is tested properly and coherent. There can be no other mixes of
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.