Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-205 - World Explorers
	1	+209 - Max Verstappen

Author

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

Content

...	...	@@ -1,51 +1,69 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
	6	+**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default.
6	6
7		-== ** Mandatory Cloud Template Upgrade - Next-generation models ** ==
	8	+{{warning}}
	9	+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.
	10	+{{/warning}}
8	8
9		-As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
	12	+== **Quicker Deployment Plan** ==
10	10
	14	+We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, 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 deployment plan will be finished much quicker now!
	15	+
	16	+== **Next Generation Architecture Default** ==
	17	+
	18	+With this release, the next generation architecture will become the default. New models will use this generation as default.
	19	+
	20	+[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
	21	+
	22	+== **Cloud Template R11 Docker - Single Lane** ==
	23	+
	24	+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.R11 Docker - Single Lane.WebHome||target="blank"]].
	25	+
	26	+== **Cloud Template R13 Docker - Double Lane** ==
	27	+
	28	+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.R13 Docker - Double Lane.WebHome||target="blank"]].
	29	+
11	11	== **Feedback Items** ==
12	12
13		-//__Improved Validation when migrating to the next-generation architecture__//
14		-To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
	32	+//__Unused properties overview__//
	33	+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:
15	15
16		-{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
	35	+* Not used by any runtime that is in the Create phase release.
	36	+* Not required by a flow that is in the Create phase release.
	37	+* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
17	17
18		-//__Improved HTTP Statistics__//
19		-To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
	39	+//__Queue explorer milliseconds__//
	40	+The queue browser now displays milliseconds in the timestamps.
20	20
21		-//__Show values on the runtime level in Deploy Architecture__//
22		-We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
	42	+//__Unused images__//
	43	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
23	23
24		-{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
25		-* JMS - The number of queues in the active release.
26		-* Messaging Container - The number of messaging integrations in the active release.
27		-* Messaging Connector - The number of messaging integrations related to this system in the active release.
28		-* API Gateway Container - The number of operations in the active release.
29		-* Event Streaming Container - The number of event processors in the active release.
	45	+//__Carwash logging__//
	46	+A new logging feature enabling us to make better choices in encryption standards will be released.
30	30
31		-There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
	48	+//__Static alerts queue consumers__//
	49	+Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
32	32
33	33	== **Bug Fixes** ==
34	34
35		-//__Gain the ability again to configure certificates in Deploy Architecture again__//
36		-In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
	53	+//__Flow Designer connection line__//
	54	+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.
37	37
38		-//__Ensure that differing container configurations deploy the correct configuration__//
39		-When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
	56	+//__Portal for migrated models__//
	57	+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.
40	40
41		-//__Remove queurying options in Manage__//
42		-To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
	59	+//__Error channel inbounds__//
	60	+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.
43	43
44	44	== **Fancy Forum Answers** ==
45	45
46	46	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:
47	47
48		-* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
	66	+* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
49	49
50	50	== **Key takeaways** ==
51	51
...	...	@@ -67,5 +67,11 @@
67	67	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
68	68
69	69	~*~* Indicates a next-generation-architecture only feature.
70		-{{/info}})))((({{toc/}}))){{/container}}
	88	+{{/info}}
	89	+)))
	90	+
	91	+(((
	92	+{{toc/}}
	93	+)))
71	71	{{/container}}
	95	+{{/container}}