Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-199 - Home Improvements
	1	+209 - Max Verstappen

Author

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

Content

...	...	@@ -2,53 +2,79 @@
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 worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
	5	+**Hi there, eMagiz developers!** We have done .....
6	6
7		-== **Next generation improvements and bug fixes** ==
	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
	8	+6:00 AM UTC instead 5:00 AM UTC. {{/warning}}
8	8
9		-//__Enhanced overview of the HTTP Statistics__//
10		-As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
	10	+== **Next Generation Architecture Default** ==
	11	+With this release, the next generation architecture will become the default. New models will use this generation as default.
11	11
12		-//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13		-In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
	13	+[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
14	14
15		-{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	15	+== **Cloud Template R11 - Single Lane** ==
	16	+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
16	16
17		-//__Forced congestion control__//
18		-To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
	18	+== **Cloud Template R13 - Double Lane** ==
19	19
20		-//__Unused images are cleaned up__//
21		-This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan.
22	22
23		-//__Improved rollup and storage of metrics when running an event streaming solution__//
24		-To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
	21	+== **Feedback Items** ==
25	25
26		-{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of July. From then on, all data before the 9th of June will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
	23	+//__Unused properties overview__//
	24	+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:
	25	+* Not used by any runtime that is in the Create phase release.
	26	+* Not required by a flow that is in the Create phase release.
	27	+* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
27	27
28		-== **Store Improvements** ==
	29	+//__Send build requests asynchronously__//
	30	+The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
29	29
30		-//__Improved importing behavior for specific use cases__//
31		-Before, it could happen that a certain placeholder that contained an asterisk (*) were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users.
	32	+//__Queue explorer milliseconds__//
	33	+The queue browser now displays milliseconds in the timestamps.
32	32
33		-== **Event Streaming - Certificate Management** ==
	35	+//__Cancel and next buttons order__//
	36	+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.
34	34
35		-//__Expired certification notification__//
36		-As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	38	+//__Unused images__//
	39	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
37	37
	41	+//__Carwash logging__//
	42	+A new logging feature enabling us to make better choices in encryption standards will be released.
	43	+
	44	+//__Static alerts queue consumers__//
	45	+Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
	46	+
	47	+== **Bug Fixes** ==
	48	+
	49	+//__Images rebuild__//
	50	+We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped.
	51	+
	52	+//__Flow Designer connection line__//
	53	+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.
	54	+
	55	+//__Portal for migrated models__//
	56	+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.
	57	+
	58	+//__Error channel inbounds__//
	59	+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.
	60	+
38	38	== **Fancy Forum Answers** ==
39	39
40	40	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:
41	41
42		-* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
43		-* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
	65	+* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
	66	+* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
	67	+* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
	68	+* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
44	44
	70	+
45	45	== **Key takeaways** ==
46	46
47		-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	+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:
48	48
49	49	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
50	50	* If you have feedback or ideas for us, talk to the Platypus
51		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	77	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
52	52	* Clear your browser cache (Ctrl + Shift + Del)
53	53	* Check out the release notes [here]
54	54	* Start thinking about how the license tracker can aid your development
...	...	@@ -61,6 +61,6 @@
61	61	{{info}}
62	62	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63	63
64		-~*~* Indicates a GEN3-only feature.
	90	+~*~* Indicates a next-generation-architecture only feature.
65	65	{{/info}})))((({{toc/}}))){{/container}}
66	66	{{/container}}