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 - Pop-up Party
	1	+198 - Great Migration

Author

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

Content

...	...	@@ -1,93 +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!** In this release, a new runtime image (LINK) will be available, including changes to our infinispan cache manager, SMB inbound channel adapter, and heap memory configuration. Moreover, we have made progress on our alerting improvement plans and have improved and added several pop-up screens. Find out all we released below!
	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
8		-== **Feedback Items** ==
9		-//__Alerting notification settings__//
10		-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.
	7	+== **3rd generation improvements and bug fixes** ==
11	11
12		-[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
	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.
13	13
14		-//__Process containers__//
15		-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.
	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}}
16	16
17		-//__Design settings__//
18		-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.
	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.
19	19
20		-[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
	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.
21	21
22		-//__Untested images__//
23		- 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.
24		-
25		-[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.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.
26	26
27		-//__Infinispan Cache Manager__//
28		-We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
29		-
30		-//__Infinispan Cache Manager error message__//
31		-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.
	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.
32	32
33		-//__Flow bump__//
34		-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.
35		-
36		-[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
	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.
37	37
38		-//__Unused support objects__//
39		-Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
40		-
41		-[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
42		-
43		-//__Deleting routes__//
44		-For clarity purposes, a confirmation pop-up will be shown when deleting routes.
45		-
46		-[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
47		-
48		-//__Debug queue__//
49		-The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it.
50		-
51		-[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
52		-
53		-== **Bug Fixes** ==
54		-//__Internal server error__//
55		-The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it.
56		-
57		-//__Namespace update__//
58		-Editing a namespace used in a message definition automatically updates the message definition & transformations.
59		-
60		-//__Error pop-up__//
61		-We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
62		-
63		-//__SMB inbound channel adapter__//
64		-The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again. For this, a new runtime image LINK is available.
65		-
66		-//__Heap memory__//
67		-The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new runtime image LINK is available.
68		-
69		-//__Classpath conflicts__//
70		-We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images.
71		-
72	72	== **Fancy Forum Answers** ==
73	73
74	74	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:
75	75
76		-* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
77		-* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
78		-* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||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"]]
79	79
80		-== **Key Takeaways** ==
	39	+== **Key takeaways** ==
81	81
82		-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:
83	83
84	84	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
85	85	* If you have feedback or ideas for us, talk to the Platypus
86		-* 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.
87	87	* Clear your browser cache (Ctrl + Shift + Del)
88		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
	47	+* Check out the release notes [here]
89	89	* Start thinking about how the license tracker can aid your development
90	90	* Start thinking about major, minor, and patch
	50	+* Upgrade to the latest build number
91	91	* Keep making great integrations
92	92
93	93	Let's stay in touch and till next time!
...	...	@@ -95,11 +95,6 @@
95	95	{{info}}
96	96	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
97	97
98		-{{/info}}
99		-)))
100		-
101		-(((
102		-{{toc/}}
103		-)))
	58	+~*~* Indicates a GEN3-only feature.
	59	+{{/info}})))((({{toc/}}))){{/container}}
104	104	{{/container}}
105		-{{/container}}