Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-204 - Found It
	1	+212 - Failover Fiesta

Author

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

Content

...	...	@@ -1,36 +1,43 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.
	6	+**Hi there, eMagiz developers!** This release...
6	6
7	7	== **Feedback Items** ==
8	8
9		-//__Improved check on nested property placeholders__//
10		-To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing.
	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"]]
11	11
12		-//__Removed outdated properties when deploying on the new generation architecture stack__//
13		-We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before in order to connect to a Kafka cluster but have become obsolete once you migrate.
	13	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
14	14
15		-{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}
	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.
16	16
17		-//__Improved performance Manage Dashboards__//
18		-We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
	18	+//__Broker queue metrics dashboards__//
	19	+It is now possible to select the MQTT broker in the queue metrics dashboards.
19	19
	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.
	23	+
	24	+
20	20	== **Bug Fixes** ==
21	21
22		-//__Errors with long stack traces or long message histories will now also show in eMagiz__//
23		-We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s).
	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.
24	24
25		-//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__//
26		-We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration.
	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.
27	27
	33	+//__Next generation block__//
	34	+Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
	35	+
28	28	== **Fancy Forum Answers** ==
29	29
30	30	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:
31	31
32		-* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]
33		-* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]]
	40	+* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
34	34
35	35	== **Key takeaways** ==
36	36
...	...	@@ -38,12 +38,11 @@
38	38
39	39	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
40	40	* If you have feedback or ideas for us, talk to the Platypus
41		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	48	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
42	42	* Clear your browser cache (Ctrl + Shift + Del)
43	43	* Check out the release notes [here]
44	44	* Start thinking about how the license tracker can aid your development
45	45	* Start thinking about major, minor, and patch
46		-* Upgrade to the latest build number
47	47	* Keep making great integrations
48	48
49	49	Let's stay in touch and till next time!
...	...	@@ -51,6 +51,11 @@
51	51	{{info}}
52	52	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
53	53
54		-~*~* Indicates a next-generation-architecture only feature.
55		-{{/info}})))((({{toc/}}))){{/container}}
	60	+{{/info}}
	61	+)))
	62	+
	63	+(((
	64	+{{toc/}}
	65	+)))
56	56	{{/container}}
	67	+{{/container}}