Last modified by Erik Bakker on 2024/08/08 15:48
From version 20.1
edited by Erik Bakker
on 2023/01/10 10:27
Change comment: There is no comment for this version
To version 13.2
edited by Erik Bakker
on 2022/06/13 14:21
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -eMagiz Runtime Generation 3
1 +fundamental-runtime-generation3
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,4 +1,9 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 +
3 +
4 +
5 += eMagiz Runtime Generation 3 =
6 +
2 2  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.
3 3  
4 4  Should you have any questions, please get in touch with academy@emagiz.com.
... ... @@ -9,10 +9,12 @@
9 9  
10 10  == 2. Key concepts ==
11 11  
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.
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.
13 13  
14 14  This runtime play a core role in the next generation architecture.
15 15  
21 +
22 +
16 16  == 3. Overview of the Generation 3 runtime ==
17 17  
18 18  === 3.1 History of runtime ===
... ... @@ -50,37 +50,19 @@
50 50  * Build number
51 51   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.
52 52  
53 -* Error handling
54 - The error handling on flow level will change in comparison to the current generation. In the new generation we will offer two options.
55 - ** Default error handling -> eMagiz will receive the errors and shows them in the Manage Dashboard
56 - ** 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.
57 - *** Including sending it to eMagiz
58 - *** Without sending it to eMagiz
59 59  
60 -* Hosted web services
61 - 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.
62 -** All-entry will be splitted to seperate entries
63 -** WSDL will be automatically generated based on your system messages
64 -** HTTP configuration is taken out of the flow and moved to Deploy -> Architecture
65 -** Configuration of endpoints is streamlined better between cloud hosted endpoints and on-premise endpoints
66 66  
67 -* Handling local file communication
68 - 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.
69 -
70 70  == 4. Key takeaways ==
71 71  
72 72  * Generation 3 runtime architecture has a series of consequences for user that need to be understood well
73 73  * The new generation architecture is the current path towards serverless, and simplyfies deployment greatly for users.
74 74  
67 +
68 +
75 75  == 5. Suggested Additional Readings ==
76 76  
77 -* [[Setup deployment plan>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-setup-deployment-plan-gen3||target="blank"]]
78 -* [[Deploy a release>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan||target="blank"]]
79 -* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-gen3||target="blank"]]
80 -* [[Migration Path - 3rd generation runtime>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3||target="blank"]]
81 -* [[Migration Path - Custom Error Handling>>doc:Main.eMagiz Support.Migration Paths.migration-path-custom-error-handling-runtime-generation-3||target="blank"]]
82 -* [[Migration Path - Hosted SOAP web service>>doc:Main.eMagiz Support.Migration Paths.migration-path-host-soap-webservice-runtime-generation-3||target="blank"]]
83 -* [[Migration Path - Hosted REST web service>>doc:Main.eMagiz Support.Migration Paths.migration-path-host-rest-webservice-runtime-generation-3||target="blank"]]
84 -* [[Volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]]
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)
85 85  
86 86  )))((({{toc/}}))){{/container}}{{/container}}