Changes for page eMagiz Runtime Generation 3

Summary

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

Details

Page properties

Default language

...	...	@@ -1,0 +1,1 @@
	1	+en

Content

...	...	@@ -9,7 +9,7 @@
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.
	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.
13	13
14	14	This runtime play a core role in the next generation architecture.
15	15
...	...	@@ -35,6 +35,8 @@
35	35
36	36	=== 3.4 Impact on Way of Working Gen2 vs. Gen3 ===
37	37
	38	+{{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}}
	39	+
38	38	* Deployment Plan
39	39	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
40	40
...	...	@@ -50,6 +50,23 @@
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
	55	+* Error handling
	56	+ The error handling on flow level will change in comparison to the current generation. In the new generation we will offer two options.
	57	+ ** Default error handling -> eMagiz will receive the errors and shows them in the Manage Dashboard
	58	+ ** 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.
	59	+ *** Including sending it to eMagiz
	60	+ *** Without sending it to eMagiz
	61	+
	62	+* Hosted web services
	63	+ 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.
	64	+** All-entry will be splitted to seperate entries
	65	+** WSDL will be automatically generated based on your system messages
	66	+** HTTP configuration is taken out of the flow and moved to Deploy -> Architecture
	67	+** Configuration of endpoints is streamlined better between cloud hosted endpoints and on-premise endpoints
	68	+
	69	+* Handling local file communication
	70	+ 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.
	71	+
53	53	== 4. Key takeaways ==
54	54
55	55	* Generation 3 runtime architecture has a series of consequences for user that need to be understood well
...	...	@@ -57,8 +57,13 @@
57	57
58	58	== 5. Suggested Additional Readings ==
59	59
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"]]
	79	+* [[Setup deployment plan>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-setup-deployment-plan-gen3||target="blank"]]
	80	+* [[Deploy a release>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan||target="blank"]]
	81	+* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-gen3||target="blank"]]
	82	+* [[Migration Path - 3rd generation runtime>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3||target="blank"]]
	83	+* [[Migration Path - Custom Error Handling>>doc:Main.eMagiz Support.Migration Paths.migration-path-custom-error-handling-runtime-generation-3||target="blank"]]
	84	+* [[Migration Path - Hosted SOAP web service>>doc:Main.eMagiz Support.Migration Paths.migration-path-host-soap-webservice-runtime-generation-3||target="blank"]]
	85	+* [[Migration Path - Hosted REST web service>>doc:Main.eMagiz Support.Migration Paths.migration-path-host-rest-webservice-runtime-generation-3||target="blank"]]
	86	+* [[Volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]]
63	63
64	64	)))((({{toc/}}))){{/container}}{{/container}}