Last modified by Erik Bakker on 2024/08/08 15:48
From version 28.1
edited by Erik Bakker
on 2024/02/20 08:31
Change comment: Renamed back-links.
To version 3.1
edited by eMagiz
on 2022/06/13 09:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,0 @@
1 -eMagiz Runtime Generation 3
Parent
... ... @@ -1,1 +1,0 @@
1 -WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.marijn
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,10 +1,19 @@
1 -{{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
1 +{{html wiki="true"}}
2 +<div class="ez-academy">
3 + <div class="ez-academy_body">
4 +<div class="doc">
5 +
6 +
7 +
8 += eMagiz Runtime Generation 3 =
9 +
4 4  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.
5 5  
6 6  Should you have any questions, please get in touch with academy@emagiz.com.
7 7  
14 +* Last update: March 17th, 2022
15 +* Required reading time: 10 minutes
16 +
8 8  == 1. Prerequisites ==
9 9  
10 10  * Advanced knowledge of the eMagiz platform
... ... @@ -11,10 +11,12 @@
11 11  
12 12  == 2. Key concepts ==
13 13  
14 -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.
23 +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.
15 15  
16 16  This runtime play a core role in the next generation architecture.
17 17  
27 +
28 +
18 18  == 3. Overview of the Generation 3 runtime ==
19 19  
20 20  === 3.1 History of runtime ===
... ... @@ -29,22 +29,14 @@
29 29  
30 30  A more modern technology compared to traditional servers is to use Docker containers. Docker provides containers that mimic servers in a specific way. A container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another. A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries and settings.
31 31  
32 -Container images become containers at runtime and in the case of Docker containers images become containers when they run on Docker Engine. From eMagiz we provide Linux based images that represent the code that processes your messages. As Docker is agnostic in terms of OS the solution can run in our cloud and on-premise on both Linux and Windows-based servers. Containers isolate software from its environment and ensure that it works uniformly despite differences for instance between development and staging.
43 +Container images become containers at runtime and in the case of Docker containers * images become containers when they run on Docker Engine. Available for both Linux and Windows-based applications, containerized software will always run the same, regardless of the infrastructure. Containers isolate software from its environment and ensure that it works uniformly despite differences for instance between development and staging.
33 33  
34 34  The runtime of eMagiz can run inside a Docker, and the runtime is made part of the docker image. In the docker image you will find other required pieces such as OS, Java, monitoring services, etc.
35 35  
36 -[[image:Main.Images.Fundamental.WebHome@fundamental-runtime-generation3-2.png]]
47 +<p align="center">[[image:fundamental-runtime-generation3-2.png||]]</p>
37 37  
38 -{{info}}
39 -More information on the install process of on-premise Docker on Linux can be found [[here>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-linux-installguide.WebHome||target="blank"]]. More information on the install process of on-premise Docker on Windows can be found [[here>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-windows-installguide.WebHome||target="blank"]].
40 -{{/info}}
41 -
42 42  === 3.4 Impact on Way of Working Gen2 vs. Gen3 ===
43 43  
44 -{{info}}
45 -See the additional readings for more detailed information on these changes and how you can migrate from the current situation to the new situation.
46 -{{/info}}
47 -
48 48  * Deployment Plan
49 49   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
50 50  
... ... @@ -59,44 +59,24 @@
59 59  
60 60  * Build number
61 61   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.
62 - It is strongly advised to have all flows on the latest build number before migrating to the next generation.
63 63  
64 -* Error handling
65 - The error handling on flow level will change in comparison to the current generation. In the new generation we will offer two options.
66 -** Default error handling -> eMagiz will receive the errors and shows them in the Manage Dashboard
67 -** Custom error handling -> For custom error handling we have two seperate options that allow you to send the error message to both a custom solution and eMagiz or only to the custom solution.
68 -*** Including sending it to eMagiz
69 -*** Without sending it to eMagiz
66 +===== Practice =====
70 70  
71 -* Hosted web services
72 - In the 3rd generation runtime you will need to migrate your hosted web service to a new configuration. Part of this new configuration will be that the following things change.
73 -** All-entry will be splitted to seperate entries
74 -** WSDL will be automatically generated based on your system messages
75 -** HTTP configuration is taken out of the flow and moved to Deploy -> Architecture
76 -** Configuration of endpoints is streamlined better between cloud hosted endpoints and on-premise endpoints
77 -
78 -* Handling local file communication
79 - As our 3rd generation runtime makes use of the docker technology your containers on default are closed off from there host. This makes them more secure, but on the same time also means that additional configuration is needed when interaction needs to happen between the host and the deployed containers.
80 -
81 81  == 4. Key takeaways ==
82 82  
83 83  * Generation 3 runtime architecture has a series of consequences for user that need to be understood well
84 84  * The new generation architecture is the current path towards serverless, and simplyfies deployment greatly for users.
85 85  
73 +
74 +
86 86  == 5. Suggested Additional Readings ==
87 87  
88 -* [[Setup deployment plan>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-setup-deployment-plan-gen3||target="blank"]]
89 -* [[Deploy a release>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.crashcourse-platform-deploy-execute-deployment-plan.WebHome||target="blank"]]
90 -* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-gen3||target="blank"]]
91 -* [[Migration Path - 3rd generation runtime>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3||target="blank"]]
92 -* [[Migration Path - Custom Error Handling>>doc:Main.eMagiz Support.Migration Paths.migration-path-custom-error-handling-runtime-generation-3||target="blank"]]
93 -* [[Migration Path - Hosted SOAP web service>>doc:Main.eMagiz Support.Migration Paths.migration-path-host-soap-webservice-runtime-generation-3||target="blank"]]
94 -* [[Migration Path - Hosted REST web service>>doc:Main.eMagiz Support.Migration Paths.migration-path-host-rest-webservice-runtime-generation-3||target="blank"]]
95 -* [[Volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]]
96 -)))
77 +* [Setting up a deployment plan](../microlearning/crashcourse-platform-deploy-setup-deployment-plan)
78 +* [Deploy a release](../microlearning/crashcourse-platform-deploy-execute-deployment-plan.md)
79 +* [Property Management](../microlearning/crashcourse-platform-deploy-property-management.md)
97 97  
98 -(((
99 -{{toc/}}
100 -)))
101 -{{/container}}
102 -{{/container}}
81 +</div>
82 +</div>
83 +</div>
84 +
85 +{{/html}}