Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-200 - Uncharted Territories
	1	+209 - Max Verstappen

Author

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

Content

...	...	@@ -2,60 +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 a lot of things that are unfortunately not quite ready to be released. As a result the output of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
	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 right-hand view within Deployment Plan context__//
10		-When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
	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		-{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
	13	+[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
13	13
14		-//__Improved timeout settings when deploying__//
15		-To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
	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		-{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	18	+== **Cloud Template R13 - Double Lane** ==
18	18
19		-//__Detailed HTTP Statistics now show user info in specific additional cases__//
20		-To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
21	21
22		-{{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}}
	21	+== **Feedback Items** ==
23	23
24		-//__Improved loading speed of Manage Dashboard__//
25		-This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
	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.
26	26
27		-== **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.
28	28
29		-//__Importing in Design is improved__//
30		-We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
	32	+//__Queue explorer milliseconds__//
	33	+The queue browser now displays milliseconds in the timestamps.
31	31
	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.
	37	+
	38	+//__Unused images__//
	39	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
	40	+
	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	+
32	32	== **Bug Fixes** ==
33	33
34		-//__Deprecated reminder pop-up removed__//
35		-We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
	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.
36	36
37		-//__Improved selection area in Flow Designer__//
38		-When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow.
	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.
39	39
40		-//__Improved Kafka settings__//
41		-For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
	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.
42	42
43		-{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
	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.
44	44
45	45	== **Fancy Forum Answers** ==
46	46
47	47	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:
48	48
49		-* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
50		-* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||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"]]
51	51
	70	+
52	52	== **Key takeaways** ==
53	53
54		-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:
55	55
56	56	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
57	57	* If you have feedback or ideas for us, talk to the Platypus
58		-* 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.
59	59	* Clear your browser cache (Ctrl + Shift + Del)
60	60	* Check out the release notes [here]
61	61	* Start thinking about how the license tracker can aid your development
...	...	@@ -68,6 +68,6 @@
68	68	{{info}}
69	69	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70	70
71		-~*~* Indicates a GEN3-only feature.
	90	+~*~* Indicates a next-generation-architecture only feature.
72	72	{{/info}})))((({{toc/}}))){{/container}}
73	73	{{/container}}