Changes for page 210 - Deployment Delights

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-209 - Max Verstappen
	1	+209 - Deployment Delights

Content

...	...	@@ -3,62 +3,49 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default.
	6	+**Hi there, eMagiz developers!** We have...
7	7
8		-{{warning}}
9		-Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC.
10		-{{/warning}}
	8	+== **Release Maintenance** ==
11	11
12		-== **Quicker Deployment Plan Execution** ==
13	13
14		-We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped. So, the deployment plan will be finished much quicker now!
15	15
16		-== **Next Generation Architecture Default** ==
17	17
18		-With this release, the next generation architecture will become the default. From now on, new models will then use this generation as the default architecture.
19	19
20		-[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
	14	+== **Feedback Items** ==
21	21
22		-== **Cloud Template R11 Docker - Single Lane** ==
	16	+//__Container version overview__//
	17	+In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
23	23
24		-This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
	19	+[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
25	25
26		-== **Cloud Template R13 Docker - Double Lane** ==
	21	+//__Unchanged containers__//
	22	+When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
27	27
28		-This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
	24	+//__Rebuilding of images__//
	25	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
29	29
30		-== **Feedback Items** ==
31	31
32		-//__Unused properties overview__//
33		-In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
	28	+== **Bug Fixes** ==
34	34
35		-* Not used by any runtime that is in the Create phase release.
36		-* Not required by a flow that is in the Create phase release.
37		-* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
	30	+//__Runtime metrics processing__//
	31	+The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
38	38
39		-//__Queue explorer milliseconds__//
40		-The queue browser now displays milliseconds in the timestamps.
	33	+//__Deployment plan__//
	34	+We solved a bug where a deployment step in the deployment plan could randomly get stuck.
41	41
42		-//__Unused images__//
43		-When a release is removed, the related unused images in the on-premises machines will be removed as well.
	36	+//__Store message merging__//
	37	+The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
44	44
45		-//__Carwash logging__//
46		-A new logging feature enabling us to make better choices in encryption standards will be released.
	39	+//__View all store items__//
	40	+An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
47	47
48		-//__Static alerts queue consumers__//
49		-Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
	42	+//__Out of memory behavior__//
	43	+We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
50	50
51		-== **Bug Fixes** ==
	45	+//__Max fetch size__//
	46	+We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
	47	+
52	52
53		-//__Flow Designer connection line__//
54		-In the Flow Designer an issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
55		-
56		-//__Portal for migrated models__//
57		-We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
58		-
59		-//__Error channel inbounds__//
60		-We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
61		-
62	62	== **Fancy Forum Answers** ==
63	63
64	64	As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: