Last modified by Erik Bakker on 2024/08/08 15:48
From version 12.1
edited by Erik Bakker
on 2022/06/13 12:37
Change comment: Imported from XAR
To version 15.1
edited by Carlijn Kokkeler
on 2022/10/05 12:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +eMagiz Runtime Generation 3
Parent
... ... @@ -1,0 +1,1 @@
1 +WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,9 +1,4 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -
3 -
4 -
5 -= eMagiz Runtime Generation 3 =
6 -
7 7  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.
8 8  
9 9  Should you have any questions, please get in touch with academy@emagiz.com.
... ... @@ -14,12 +14,10 @@
14 14  
15 15  == 2. Key concepts ==
16 16  
17 -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.
12 +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.
18 18  
19 19  This runtime play a core role in the next generation architecture.
20 20  
21 -
22 -
23 23  == 3. Overview of the Generation 3 runtime ==
24 24  
25 25  === 3.1 History of runtime ===
... ... @@ -57,19 +57,15 @@
57 57  * Build number
58 58   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.
59 59  
60 -
61 -
62 62  == 4. Key takeaways ==
63 63  
64 64  * Generation 3 runtime architecture has a series of consequences for user that need to be understood well
65 65  * The new generation architecture is the current path towards serverless, and simplyfies deployment greatly for users.
66 66  
67 -
68 -
69 69  == 5. Suggested Additional Readings ==
70 70  
71 -* [Setting up a deployment plan](../microlearning/crashcourse-platform-deploy-setup-deployment-plan)
72 -* [Deploy a release](../microlearning/crashcourse-platform-deploy-execute-deployment-plan.md)
73 -* [Property Management](../microlearning/crashcourse-platform-deploy-property-management.md)
60 +* [[Setup deployment plan>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-setup-deployment-plan.WebHome||target="blank"]]
61 +* [[Deploy a release>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan.WebHome||target="blank"]]
62 +* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management.WebHome||target="blank"]]
74 74  
75 75  )))((({{toc/}}))){{/container}}{{/container}}