Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-197 - Pay Attention
	1	+188 - Close Encounters

Content

...	...	@@ -2,55 +2,72 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** In the last few weeks, we have work hard on improving our next generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore there are several smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
	5	+**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community.
6	6
7		-== **Event streaming alerting** ==
	7	+== **3rd generation runtime bolstering** ==
8	8
9		-With this release we expand our alerting functionality into the event streaming pattern. As of now one new "static" alert is introduced for all clients (using event streaming) and two "dynamic" alerts are introduced that you can configure yourself if there is need for it.
	9	+This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it.
10	10
11		-The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights whether messages on it are deleted due to a size or time constraint. In cases where data is deleted becomes the topic was too full way before the messages should have been removed as a result of the retention hours constraint this alert can be seen as an indication that messages might be deleted before consumer groups had the option to consume the messages.
	11	+//__Migration of JMS backup configuration improved__//
12	12
13		-The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
	13	+//__Prechecks on Upgrade option made available for 3rd generation runtime__//
14	14
15		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
	15	+//__Autogenerated exits can be deployed at once__//
16	16
17		-The first new "dynamic" alert allows you to raise an alert once the total number of messages on one (or more topics) is less than a certain number per defined time unit. So for example you can configure an alert once the number of message placed on a topic called "Exception" is less than 15 messages within 5 minutes.
	17	+//__Code mapping functionality available on 3rd generation runtime__//
18	18
19		-[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
	19	+//__Improved the performance of deploying or activating a release__//
20	20
21		-The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups is more than X number of messages behind on one or more topics. The configuration of this is comparable as we saw before.
	21	+//__Failing runtimes won't be restarted indefinetly anymore__//
22	22
23		-For more information on the generic way of working surrounding alerting please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
	23	+== **Exportable Release Audit** ~* ==
24	24
25		-== **3rd generation improvements** ==
	25	+On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
26	26
27		-//__Increased grace period for shutdown__//
28		-In this release, we have increased the grace period a container gets to shutdown before it is forcefully shutdown. This should reduce the chance of unwanted failover behavior to pop-up within your model.
	27	+[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
29	29
30		-//__Update at once or not__//
31		-This release fixes 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.
	29	+{{warning}}Note that the following restrictions apply when exporting an audit document:
	30	+ * Changes made on definition and transformation level are **not** restored
	31	+ * You will **not** be able to restore to any flow version that was created before October 17th, 2022
	32	+ * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
	33	+ * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
32	32
33		-//__Improved user feedback while executing a deployment plan__//
34		-This release introduces additional feedback to the user when the deployment plan is executed. This is noticeable when a step cannot be executed properly. The relevant information of why this cannot be executed is shown to the user. This way they can take this information and act upon it instead of assuming everything went well.
	35	+== **Feedback items ** ==
35	35
36		-//__Improved auto-healing when running in a hybrid situation__//
37		-In situations where you run in a hybrid situation (i.e. partly next-gen and partly the current generation) we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next generation architecture.
	37	+We have also solved other feedback items besides the flow designer's critical updates.
38	38
39		-== **Feedback items ** ==
	39	+//__Data Sink Refactor__//
	40	+We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end we will contact your seperately.
40	40
41		-//__Make sure the message format can be viewed without "Start editing"__//
42		-With this release, we have ensured that when you navigate to Design -> System message you can see the message format (i.e. XML, JSON or EDI) without entering the "Start Editing" mode.
	42	+//__Improved naming convention on Store related pages__//
	43	+We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
43	43
44		-//__Various styling improvements in the flow testing functionality__//
45		-Various smaller styling improvements have been added to the flow testing functionality to improve the overall user experience. For a complete list and more details please check out the release notes.
	45	+//__Press "Enter" to search on multiple pages__//
	46	+In our Daemon Switch release we added functionality that allowed you to press **Enter** to search on the property overview page. With this release we have added this functionality to many more pages across the portal. The complete list is as follows
46	46
	48	+* Deploy → Deployment Plan
	49	+* Deploy → Properties → History
	50	+* Deploy → User Management → Roles
	51	+* Manage → Error Messages → Error Messages
	52	+* Manage → Error Messages → Flows with Error Messages
	53	+* Manage → Error Messages → Exceptions of Error Messages
	54	+* Manage → Log Entries
	55	+* Manage → Alerts
	56	+* Manage → Triggers
	57	+* Manage → Tags – Cant find (only Gen2)
	58	+* Manage → Notifications
	59	+* Manage → Notification Settings
	60	+* Manage → Data Usage → History
	61	+* Manage → Code mappings → All tabs
	62	+
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		-* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
52		-* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
53		-* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
	67	+* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
	68	+* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
	69	+* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
	70	+* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
54	54
55	55	== **Key takeaways** ==
56	56