Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-211 - Log Luminary
	1	+212 - Failover Fiesta

Content

...	...	@@ -3,58 +3,42 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!**
	6	+**Hi there, eMagiz developers!** This release...
7	7
8		-== **TBD** ==
9		-
10		-
11		-
12	12	== **Feedback Items** ==
13	13
14		-//__Missing properties overview__//
15		-The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
	10	+//__Failover setup__//
	11	+New components have been created to support a failover setup. More information can be found [[here>>doc:Main.Release Information.Runtime Images.V2.1.0||target="blank"]]
16	16
17		-ADD FIGURE
	13	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
18	18
19		-//__Container version overview__//
20		-Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
	15	+//__External recipients emailaddress__//
	16	+The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
21	21
22		-[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
	18	+//__Broker queue metrics dashboards__//
	19	+It is now possible to select the MQTT broker in the queue metrics dashboards.
23	23
24		-//__Improved deployment process__//
25		-The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
	21	+//__Runtime image version__//
	22	+The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
26	26
27		-//__Rebuilding of images__//
28		-Changing the list of flows that should run on a container will now trigger the rebuilding of images.
29	29
30	30	== **Bug Fixes** ==
31	31
32		-//__Runtime metrics processing__//
33		-The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
	27	+//__Message throughput__//
	28	+The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
34	34
35		-//__Deployment plan__//
36		-We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
	30	+//__Cloud template upgrade incorrect rollback__//
	31	+An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
37	37
38		-//__View all store items__//
39		-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.
	33	+//__Next generation block__//
	34	+Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
40	40
41		-//__Out of memory behavior__//
42		-We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
43		-
44		-//__Max fetch size__//
45		-In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
46		-
47	47	== **Fancy Forum Answers** ==
48	48
49	49	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:
50	50
51		-* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
52		-* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
53		-* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
54		-* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
55		-* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
	40	+* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
56	56
57		-
58	58	== **Key takeaways** ==
59	59
60	60	Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
...	...	@@ -66,7 +66,6 @@
66	66	* Check out the release notes [here]
67	67	* Start thinking about how the license tracker can aid your development
68	68	* Start thinking about major, minor, and patch
69		-* Upgrade to the latest build number
70	70	* Keep making great integrations
71	71
72	72	Let's stay in touch and till next time!
...	...	@@ -74,7 +74,6 @@
74	74	{{info}}
75	75	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
76	76
77		-~*~* Indicates a next-generation-architecture only feature.
78	78	{{/info}}
79	79	)))
80	80