Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-212 - Failover Fiesta
	1	+198 - Great Migration

Author

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

Content

...	...	@@ -1,50 +1,53 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** This release contains single and double lane cloud template updates, both non-service affecting. Moreover, work has been done to better support a failover setup. Lastly, some bug fixes were done regarding the message merging tool and catalog topic defintions.
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.
7	7
8		-== **Cloud Template R20 - Double Lane** ==
	7	+== **3rd generation improvements and bug fixes** ==
9	9
10		-This release introduces a new non-service affecting cloud template for all our customers running in a double-lane setup. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R20 - Double lane.WebHome||target="blank"]].
	9	+//__"Stop" action when running a hybrid situation is not causing issues anymore__//
	10	+Before, it could happen when running a double-lane setup in a hybrid situation (i.e., karaf, based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release, that behavior is changed.
11	11
12		-== **Cloud Template R27 - Single Lane** ==
	12	+{{info}}Note that this fix is part of a new runtime image for the karaf-based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
13	13
14		-This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R27 - Single lane.WebHome||target="blank"]].
	14	+//__Improved efficiency in deploying a release__//
	15	+This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.
15	15
16		-== **Feedback Items** ==
	17	+//__Removed specific dependencies between Deploy Architecture and Releases__//
	18	+In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.
17	17
18		-//__Failover setup__//
19		-New components have been created to support a failover setup. Moreover, two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
	20	+//__Improved validation errors on the invalid configuration of HTTP outbound components__//
	21	+This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
20	20
21		-== **Bug Fixes** ==
	23	+//__Improved migration behavior__//
	24	+This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
	25	+A smoother migration of your JMS (and backup JMS) process.
	26	+Shortening of names that otherwise would be too long, additional feedback given to the user.
	27	+Feedback when the migration process is finished.
22	22
23		-//__Message merging tool__//
24		-The message merging tool has been fixed to allow merging a store item message model into your own message models. In some rare cases your CDM message may be broken due to incorrect data. In those cases, the message mapping and message merge functionalities will be broken as well. If this broken data is detected when navigating to CDM-message-related pages, you will be able to clean your CDM message.
	29	+//__Additional checks when deploying__//
	30	+This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
25	25
26		-//__Catalog topic definitions__//
27		-It is now possible to generate a JSON Example of a topic whose schema has nested elements. Before, an error would occur when trying to generate a JSON example in this case.
28		-
29	29	== **Fancy Forum Answers** ==
30	30
31	31	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:
32	32
33		-* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
34		-* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
35		-* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
	36	+* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
	37	+* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
36	36
37	37	== **Key takeaways** ==
38	38
39		-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:
	41	+Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
40	40
41	41	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
42	42	* If you have feedback or ideas for us, talk to the Platypus
43		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	45	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
44	44	* Clear your browser cache (Ctrl + Shift + Del)
45	45	* Check out the release notes [here]
46	46	* Start thinking about how the license tracker can aid your development
47	47	* Start thinking about major, minor, and patch
	50	+* Upgrade to the latest build number
48	48	* Keep making great integrations
49	49
50	50	Let's stay in touch and till next time!
...	...	@@ -52,11 +52,6 @@
52	52	{{info}}
53	53	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
54	54
55		-{{/info}}
56		-)))
57		-
58		-(((
59		-{{toc/}}
60		-)))
	58	+~*~* Indicates a GEN3-only feature.
	59	+{{/info}})))((({{toc/}}))){{/container}}
61	61	{{/container}}
62		-{{/container}}