Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-225 - TBD
	1	+198 - Great Migration

Author

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

Content

...	...	@@ -1,74 +1,53 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!**
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.
7	7
	7	+== **3rd generation improvements and bug fixes** ==
8	8
9		-== **Feedback Items** ==
10		-//__Alerting notification settings__//
11		-The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature.
	9	+//__"Stop" action when running a hybrid situation is not causing issues anymore__//
	10	+Before, it could happen when running a double-lane setup in a hybrid situation (i.e., karaf, based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release, that behavior is changed.
12	12
13		-[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
	12	+{{info}}Note that this fix is part of a new runtime image for the karaf-based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
14	14
15		-//__Process containers__//
16		-If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern.
	14	+//__Improved efficiency in deploying a release__//
	15	+This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.
17	17
18		-//__Design settings__//
19		-When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
	17	+//__Removed specific dependencies between Deploy Architecture and Releases__//
	18	+In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.
20	20
21		-[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
	20	+//__Improved validation errors on the invalid configuration of HTTP outbound components__//
	21	+This release fixes and 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.
22	22
23		-//__Untested images__//
24		- A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before.
25		-
26		-[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
	23	+//__Improved migration behavior__//
	24	+This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
	25	+A smoother migration of your JMS (and backup JMS) process.
	26	+Shortening of names that otherwise would be too long, additional feedback given to the user.
	27	+Feedback when the migration process is finished.
27	27
28		-//__Infinispan Cache Manager__//
29		-We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
30		-
31		-//__Infinispan Cache Manager error message__//
32		-We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new runtime image LINK is available.
	29	+//__Additional checks when deploying__//
	30	+This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
33	33
34		-//__Flow bump__//
35		-When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description.
36		-
37		-IMAGE
38		-
39		-//__Unused support objects__//
40		-Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
41		-
42		-[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
43		-
44		-//__Deleting routes__//
45		-For clarity purposes, a confirmation pop-up will be shown when deleting routes.
46		-
47		-[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
48		-
49		-== **Bug Fixes** ==
50		-
51		-
52		-
53		-
54		-
55	55	== **Fancy Forum Answers** ==
56	56
57	57	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:
58	58
59		-* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
	36	+* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
	37	+* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
60	60
61		-== **Key Takeaways** ==
	39	+== **Key takeaways** ==
62	62
63		-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:
	41	+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:
64	64
65	65	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
66	66	* If you have feedback or ideas for us, talk to the Platypus
67		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	45	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
68	68	* Clear your browser cache (Ctrl + Shift + Del)
69		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
	47	+* Check out the release notes [here]
70	70	* Start thinking about how the license tracker can aid your development
71	71	* Start thinking about major, minor, and patch
	50	+* Upgrade to the latest build number
72	72	* Keep making great integrations
73	73
74	74	Let's stay in touch and till next time!
...	...	@@ -76,11 +76,6 @@
76	76	{{info}}
77	77	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78	78
79		-{{/info}}
80		-)))
81		-
82		-(((
83		-{{toc/}}
84		-)))
	58	+~*~* Indicates a GEN3-only feature.
	59	+{{/info}})))((({{toc/}}))){{/container}}
85	85	{{/container}}
86		-{{/container}}