Last modified by Erik Bakker on 2024/08/08 15:48
From version 25.1
edited by Carlijn Kokkeler
on 2023/10/06 09:10
Change comment: There is no comment for this version
To version 30.1
edited by Erik Bakker
on 2024/08/08 14:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,4 +1,6 @@
1 -{{container}}{{container layoutStyle="columns"}}(((
1 +{{container}}
2 +{{container layoutStyle="columns"}}
3 +(((
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.
... ... @@ -17,60 +17,67 @@
17 17  
18 18  === 3.1 History of runtime ===
19 19  
20 -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.
22 +In the last few years, eMagiz has evolved from a local, on-premises deployment platform to a cloud-first platform. At the inception of the eMagiz runtime, we provided a process that could only run locally on a (dedicated) server of clients. We refer to that as Generation 1 runtime. With the requirement to deploy eMagiz runtime in the Cloud, we updated the runtime to Generation 2, including the OSGI and Karaf framework that allowed remote running runtimes. Our next step, explained below, is then referred to as Generation 3.
21 21  
22 22  === 3.2 Spring Boot framework ===
23 23  
24 -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.
26 +The ambition of eMagiz is 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 required 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 a means to measure many more things in the context of log entries and runtime metrics.
25 25  
26 26  === 3.3 Docker technology ===
27 27  
28 -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.
30 +A more modern technology than traditional servers is using 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.
29 29  
30 -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.
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 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.
31 31  
32 -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.
34 +The eMagiz runtime can run inside a Docker, and it is made part of the Docker image. You will find other required pieces in the Docker image, such as the OS, Java, monitoring services, and more.
33 33  
34 34  [[image:Main.Images.Fundamental.WebHome@fundamental-runtime-generation3-2.png]]
35 35  
36 -{{info}}More information on the install process of on-premise Docker can be found [[here>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-installguide.WebHome||target="blank"]]{{/info}}
38 +{{info}}
39 +More information on the installation 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}}
37 37  
38 38  === 3.4 Impact on Way of Working Gen2 vs. Gen3 ===
39 39  
40 -{{info}}See the additional readings for more detailed information on these changes and how you can migrate from the current situation to the new situation.{{/info}}
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}}
41 41  
42 42  * Deployment Plan
43 - 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
49 + ** The deployment has a new option called Deploy runtimes. These steps will be part of a default plan or can be added as a separate line. Effectively, once a runtime is deployed as part of a Docker image, the image needs to be loaded and executed. That means the current image, including all flows, will be replaced with a new one. This makes the deployment simple and fast. The option means that all runtime on a machine will be deployed in minutes.
44 44  
45 45  * Releases
46 - The releases functionality is used for defining the Docker image. Setting the release means creating a new Docker image.
52 + ** The release functionality defines the Docker image. Setting the release means creating a new Docker image.
47 47  
48 48  * Deploy Architecture
49 - 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.
55 + ** You can see the running status of a Docker image at every runtime. The Docker image can be switched on or off, and flows can't be selectively switched on or off.
50 50  
57 +* Runtime Overview
58 + ** This overview shows all runtimes and their corresponding status. This is a replacement for the Runtime Dashboard.
59 +
51 51  * Properties
52 - 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 the previous generation of runtime, properties were loaded at the 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 of creating a new release once a property is changed.
53 53  
54 54  * Build number
55 - 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.
56 - It is strongly advised to have all flows on the latest build number before migrating to the next generation.
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.
65 + It is strongly advised that all flows be on the latest build number before migrating to the next generation.
57 57  
58 58  * Error handling
59 - The error handling on flow level will change in comparison to the current generation. In the new generation we will offer two options.
60 - ** Default error handling -> eMagiz will receive the errors and shows them in the Manage Dashboard
61 - ** 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.
62 - *** Including sending it to eMagiz
63 - *** Without sending it to eMagiz
68 + ** The error handling on the flow level will change compared to the current generation. For the new generation, we will offer two options.
69 + *** Default error handling -> eMagiz will receive the errors and show them in the Manage Dashboard
70 + *** Custom error handling -> We have two separate options that allow you to send the error message to a custom solution and eMagiz or only to the custom solution.
71 + **** Including sending it to eMagiz
72 + **** Without sending it to eMagiz
64 64  
65 65  * Hosted web services
66 - 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.
67 -** All-entry will be splitted to seperate entries
68 -** WSDL will be automatically generated based on your system messages
69 -** HTTP configuration is taken out of the flow and moved to Deploy -> Architecture
70 -** Configuration of endpoints is streamlined better between cloud hosted endpoints and on-premise endpoints
75 +** In the third-generation runtime, you will need to migrate your hosted web service to a new configuration. The following will change in this new configuration.
76 +*** All-entry will be split into separate entries
77 +*** WSDL will be automatically generated based on your system messages
78 +*** HTTP configuration is taken out of the flow and moved to Deploy -> Architecture
79 +*** Configuration of endpoints is streamlined better between cloud-hosted endpoints and on-premise endpoints
71 71  
72 72  * Handling local file communication
73 - 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.
82 +** As our third-generation runtime uses Docker technology, your containers are, by default, closed off from their host. This makes them more secure, but it also means that additional configuration is needed when interaction needs to happen between the host and the deployed containers.
74 74  
75 75  == 4. Key takeaways ==
76 76  
... ... @@ -80,7 +80,7 @@
80 80  == 5. Suggested Additional Readings ==
81 81  
82 82  * [[Setup deployment plan>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-setup-deployment-plan-gen3||target="blank"]]
83 -* [[Deploy a release>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan||target="blank"]]
92 +* [[Deploy a release>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.crashcourse-platform-deploy-execute-deployment-plan.WebHome||target="blank"]]
84 84  * [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-gen3||target="blank"]]
85 85  * [[Migration Path - 3rd generation runtime>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3||target="blank"]]
86 86  * [[Migration Path - Custom Error Handling>>doc:Main.eMagiz Support.Migration Paths.migration-path-custom-error-handling-runtime-generation-3||target="blank"]]
... ... @@ -87,5 +87,10 @@
87 87  * [[Migration Path - Hosted SOAP web service>>doc:Main.eMagiz Support.Migration Paths.migration-path-host-soap-webservice-runtime-generation-3||target="blank"]]
88 88  * [[Migration Path - Hosted REST web service>>doc:Main.eMagiz Support.Migration Paths.migration-path-host-rest-webservice-runtime-generation-3||target="blank"]]
89 89  * [[Volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]]
99 +)))
90 90  
91 -)))((({{toc/}}))){{/container}}{{/container}}
101 +(((
102 +{{toc/}}
103 +)))
104 +{{/container}}
105 +{{/container}}