Changes for page eMagiz Runtime Generation 3

Summary

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

Details

Page properties

Content

...	...	@@ -46,40 +46,40 @@
46	46	{{/info}}
47	47
48	48	* Deployment Plan
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.
	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.
50	50
51	51	* Releases
52		- The release functionality defines 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.
53	53
54	54	* Deploy Architecture
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.
	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.
56	56
57	57	* Runtime Overview
58		-This overview shows all runtimes and their corresponding status. This is a replacement for the Runtime Dashboard.
	58	+ ** This overview shows all runtimes and their corresponding status. This is a replacement for the Runtime Dashboard.
59	59
60	60	* Properties
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.
	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.
62	62
63	63	* Build number
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.
	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	65	It is strongly advised that all flows be on the latest build number before migrating to the next generation.
66	66
67	67	* Error handling
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
	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
73	73
74	74	* Hosted web services
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
	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
80	80
81	81	* Handling local file communication
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.
	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.
83	83
84	84	== 4. Key takeaways ==
85	85