Changes for page eMagiz Runtime Generation 3

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,6 +1,4 @@
1		-{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	1	+{{container}}{{container layoutStyle="columns"}}(((
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.
...	...	@@ -35,15 +35,11 @@
35	35
36	36	[[image:Main.Images.Fundamental.WebHome@fundamental-runtime-generation3-2.png]]
37	37
38		-{{info}}
39		-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-linux-installguide.WebHome||target="blank"]]
40		-{{/info}}
	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}}
41	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}}
	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}}
47	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
...	...	@@ -63,10 +63,10 @@
63	63
64	64	* Error handling
65	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
	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
70	70
71	71	* Hosted web services
72	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.
...	...	@@ -93,10 +93,5 @@
93	93	* [[Migration Path - Hosted SOAP web service>>doc:Main.eMagiz Support.Migration Paths.migration-path-host-soap-webservice-runtime-generation-3||target="blank"]]
94	94	* [[Migration Path - Hosted REST web service>>doc:Main.eMagiz Support.Migration Paths.migration-path-host-rest-webservice-runtime-generation-3||target="blank"]]
95	95	* [[Volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]]
96		-)))
97	97
98		-(((
99		-{{toc/}}
100		-)))
101		-{{/container}}
102		-{{/container}}
	91	+)))((({{toc/}}))){{/container}}{{/container}}