Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 595.1
edited by CarlijnKokkeler
on 2024/07/16 12:06
Change comment: There is no comment for this version
To version 347.1
edited by CarlijnKokkeler
on 2024/01/17 09:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - TBD
1 +212 - Failover Fiesta
Content
... ... @@ -3,47 +3,38 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
6 +**Hi there, eMagiz developers!** This release contains single and double lane cloud template updates, both non-service affecting. Moreover, work has been done to better support a failover setup. Lastly, some bug fixes were done regarding the message merging tool and catalog topic defintions.
7 7  
8 +== **Cloud Template R20 - Double Lane** ==
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.
10 +This release introduces a new non-service affecting cloud template for all our customers running in a double-lane setup. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R20 - Double lane.WebHome||target="blank"]].
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
12 +== **Cloud Template R27 - Single Lane** ==
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 +This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R27 - Single lane.WebHome||target="blank"]].
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.
16 +== **Feedback Items** ==
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
18 +//__Failover setup__//
19 +New components have been created to support a failover setup. Moreover, two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
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]]
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.
33 -
34 34  == **Bug Fixes** ==
35 35  
23 +//__Message merging tool__//
24 +We have improved our merging functionality within our Store offering to avoid unexpected results after merging. These unexpected results would lead to a broken Design phase on the data model level. If you have encountered this issue, you can manually clean your CDM message by removing the entities from the tree view and the canvas and correcting the CDM itself accordingly.
36 36  
26 +//__Catalog topic definitions__//
27 +Before, an error would occur in the Catalog page when generating an example JSON message of a topic definition that has nested elements. This issue is now fixed and generating a sample JSON message for such topic definition is possible.
37 37  
38 -
39 -
40 40  == **Fancy Forum Answers** ==
41 41  
42 42  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:
43 43  
44 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
33 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
34 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
35 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
45 45  
46 -== **Key Takeaways** ==
37 +== **Key takeaways** ==
47 47  
48 48  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:
49 49  
... ... @@ -51,7 +51,7 @@
51 51  * If you have feedback or ideas for us, talk to the Platypus
52 52  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
53 53  * Clear your browser cache (Ctrl + Shift + Del)
54 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
45 +* Check out the release notes [here]
55 55  * Start thinking about how the license tracker can aid your development
56 56  * Start thinking about major, minor, and patch
57 57  * Keep making great integrations