Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-209 - Max Verstappen
	1	+194 - Big Leap

Author

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

Content

...	...	@@ -2,78 +2,74 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** We have done .....
	5	+**Hi there, eMagiz developers!** In the last couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
6	6
7		-{{warning}}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. {{/warning}}
	7	+== **3rd generation improvements** ==
8	8
9		-== **Quicker Deployment Plan** ==
10		-We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now!
	9	+//__Better feedback in error log when a corrupt stylesheet is encountered__//
	10	+We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
11	11
12		-== **Next Generation Architecture Default** ==
13		-With this release, the next generation architecture will become the default. New models will use this generation as default.
	12	+//__Better internal error handling to avoid unnecessary alerting and notifications__//
	13	+We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
14	14
15		-[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
	15	+//__Improved Manage Dashboard__//
	16	+This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
16	16
17		-== **Cloud Template R11 Docker - Single Lane** ==
18		-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.WebHome||target="blank"]].
	18	+//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
	19	+When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes.
19	19
20		-== **Cloud Template R13 Docker - Double Lane** ==
21		-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.WebHome||target="blank"]].
	21	+//__Improved process of deploy preparation__//
	22	+With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
22	22
23		-== **Feedback Items** ==
	24	+//__Improved migration of Streaming container__//
	25	+When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
24	24
25		-//__Unused properties overview__//
26		-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:
27		-* Not used by any runtime that is in the Create phase release.
28		-* Not required by a flow that is in the Create phase release.
29		-* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
	27	+//__Add History to Notifications in Manage__//
	28	+To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications.
30	30
31		-//__Send build requests asynchronously__//
32		-The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
	30	+//__Improved Manage phase for Event Streaming__//
	31	+Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you.
33	33
34		-//__Queue explorer milliseconds__//
35		-The queue browser now displays milliseconds in the timestamps.
	33	+//__Improved help text for network volumes__//
	34	+With this release we have improved the help text that explains network volumes and how to use them within our solution.
36	36
37		-//__Cancel and next buttons order__//
38		-The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
	36	+{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
39	39
40		-//__Unused images__//
41		-When a release is removed, the related unused images in the on-premises machines will be removed as well.
	38	+== **Feedback items ** ==
42	42
43		-//__Carwash logging__//
44		-A new logging feature enabling us to make better choices in encryption standards will be released.
	40	+//__Removed OData as option for an API Gateway operation__//
	41	+With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
45	45
46		-//__Static alerts queue consumers__//
47		-Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
	43	+//__Changes in API Gateway operation paths is automatically updated in Create__//
	44	+When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
48	48
49		-== **Bug Fixes** ==
	46	+{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
50	50
51		-//__Flow Designer connection line__//
52		-In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
	48	+== **Bug fixes ** ==
53	53
54		-//__Portal for migrated models__//
55		-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.
	50	+//__Prevent endless loop in Deploy -> User Management__//
	51	+With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
56	56
57		-//__Error channel inbounds__//
58		-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.
	53	+{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
59	59
	55	+//__Update error handling during migration to the 3rd generation runtime__//
	56	+As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
	57	+
60	60	== **Fancy Forum Answers** ==
61	61
62	62	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:
63	63
64		-* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
65		-* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
66		-* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
67		-* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
	62	+* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
	63	+* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
	64	+* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
68	68
69		-
70	70	== **Key takeaways** ==
71	71
72		-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:
	68	+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:
73	73
74	74	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
75	75	* If you have feedback or ideas for us, talk to the Platypus
76		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	72	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
77	77	* Clear your browser cache (Ctrl + Shift + Del)
78	78	* Check out the release notes [here]
79	79	* Start thinking about how the license tracker can aid your development
...	...	@@ -86,6 +86,6 @@
86	86	{{info}}
87	87	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
88	88
89		-~*~* Indicates a next-generation-architecture only feature.
	85	+~*~* Indicates a GEN3-only feature.
90	90	{{/info}})))((({{toc/}}))){{/container}}
91	91	{{/container}}