Last modified by Erik Bakker on 2024/02/20 08:31
From version 1.1
edited by eMagiz
on 2022/06/13 09:29
Change comment: There is no comment for this version
To version 2.1
edited by eMagiz
on 2022/06/13 09:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,20 +1,12 @@
1 1  {{html wiki="true"}}
2 2  <div class="ez-academy">
3 3   <div class="ez-academy_body">
4 -
5 -
6 - <li class="doc-nav__item"><a href="../../docs/fundamental/index_academy_fundamental_all" class="doc-nav__link">Home</a></li>
7 -
8 -
9 -
10 -
11 -
12 12  <div class="doc">
13 13  
14 14  
15 15  
16 16  = eMagiz Runtime Generation 3 =
17 -
9 +
18 18  In this fundamental, the focus will be on the runtimes of eMagiz and notably the next generation runtime. The internal projectname is called Generation 3, which we'll use here for now.
19 19  
20 20  Should you have any questions, please get in touch with academy@emagiz.com.
... ... @@ -26,22 +26,23 @@
26 26  
27 27  * Advanced knowledge of the eMagiz platform
28 28  
29 -
30 30  == 2. Key concepts ==
22 +
31 31  The first thing to consider is the eMagiz runtime. This is the Java based application container where the generated code of eMagiz flows is deployed and put into operation. That runtime is something you can download in the Deploy --> Containers section as a zipfile, and make active on your local laptop or machine. The way to invoke the Java application container is to execute the karaf.bat (which refers to the framework we use for that). For runtimes that are deployed, the karaf.bat is the executable refered in the services of the DMZ server of the client.
32 32  
33 -This runtime play a core role in the next generation architecture.
25 +This runtime play a core role in the next generation architecture.
34 34  
35 35  
36 -
28 +
37 37  == 3. Overview of the Generation 3 runtime ==
38 38  
39 39  === 3.1 History of runtime ===
32 +
40 40  In the last years eMagiz evolved from a local, on-premises deployment platfrom to a Cloud-first platform. In the inception of the eMagiz runtime, we where able to provide a process that could only run locally on a (dedicated) server of clients. We refer that as Generation 1 runtime. With the requirement to deploy eMagiz runtime also in the Cloud, we updated the runtime to Generation 2. Which included the OSGI and Karaf framework that allowed to remotely manage runtimes. Our next step explained below is then referred as Generation 3.
41 41  
42 42  === 3.2 Spring Boot framework ===
43 43  
44 -The ambition of eMagiz to work towards serverless Cloud environments, where the eMagiz runtime can be made operational. A bigger portion of our platform leverages the Spring Integration framework, and the Spring Boot framework provides the requirement components to form a Java based application container that can run on Docker technology. It was therefore logical to migrate the existing runtime to that framework, making OSGI and Karaf obsolete. Furthermore, the Spring Boot framework provides means to measure many more things in the context of log entries and runtime metrics.
37 +The ambition of eMagiz to work towards serverless Cloud environments, where the eMagiz runtime can be made operational. A bigger portion of our platform leverages the Spring Integration framework, and the Spring Boot framework provides the requirement components to form a Java based application container that can run on Docker technology. It was therefore logical to migrate the existing runtime to that framework, making OSGI and Karaf obsolete. Furthermore, the Spring Boot framework provides means to measure many more things in the context of log entries and runtime metrics.
45 45  
46 46  === 3.3 Docker technology ===
47 47  
... ... @@ -56,19 +56,19 @@
56 56  === 3.4 Impact on Way of Working Gen2 vs. Gen3 ===
57 57  
58 58  * Deployment Plan
59 -The deployment has a new option called Deploy runtimes. These steps will be part of a default plan, or can be added as seperate line. Effectively, once a runtime is deployed as part of a Docker image, the image needs to be loaded and executed. That means that current image including all flows will be replaced with a new image. This makes the deployment simple and fast. The option means that all runtimes of a machine will be deployed in matter of seconds
52 + The deployment has a new option called Deploy runtimes. These steps will be part of a default plan, or can be added as seperate line. Effectively, once a runtime is deployed as part of a Docker image, the image needs to be loaded and executed. That means that current image including all flows will be replaced with a new image. This makes the deployment simple and fast. The option means that all runtimes of a machine will be deployed in matter of seconds
60 60  
61 61  * Releases
62 -The releases functionality is used for defining the Docker image. Setting the release means creating a new Docker image.
55 + The releases functionality is used for defining the Docker image. Setting the release means creating a new Docker image.
63 63  
64 64  * Deploy Architecture
65 -On every runtime you can see the running status of a Docker image. In a way, this a replacement for the Runtime Dashboard. The docker image is switched on or off, and flows can't be selectively switched on or off.
58 + On every runtime you can see the running status of a Docker image. In a way, this a replacement for the Runtime Dashboard. The docker image is switched on or off, and flows can't be selectively switched on or off.
66 66  
67 67  * Properties
68 -In previous generation runtime, properties where loaded at runtime level (in a way). Updating a property meant stopping and starting a flow to effectuate the property change. Now, the properties are made part of the Docker image. That results in the necessity to create a new release once a property is changed.
61 + In previous generation runtime, properties where loaded at runtime level (in a way). Updating a property meant stopping and starting a flow to effectuate the property change. Now, the properties are made part of the Docker image. That results in the necessity to create a new release once a property is changed.
69 69  
70 70  * Build number
71 -The notion of build numbers no longer exists in the new runtime. Or not so explicitly as before. The Docker image will load the required libraries when creating the runtime image, and always use the latest.
64 + The notion of build numbers no longer exists in the new runtime. Or not so explicitly as before. The Docker image will load the required libraries when creating the runtime image, and always use the latest.
72 72  
73 73  ===== Practice =====
74 74  
... ... @@ -79,7 +79,6 @@
79 79  
80 80  
81 81  
82 -
83 83  == 5. Suggested Additional Readings ==
84 84  
85 85  * [Setting up a deployment plan](../microlearning/crashcourse-platform-deploy-setup-deployment-plan)
... ... @@ -87,7 +87,7 @@
87 87  * [Property Management](../microlearning/crashcourse-platform-deploy-property-management.md)
88 88  
89 89  </div>
90 -</main>
91 91  </div>
92 92  </div>
84 +
93 93  {{/html}}