Skip to Content

Changes for page 214 - System Symphony

Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 379.1
edited by Carlijn Kokkeler
on 2024/02/12 16:37
Change comment: There is no comment for this version
To version 348.1
edited by Carlijn Kokkeler
on 2024/01/18 16:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -214 - System Symphony
1 +212 - Failover Fiesta
Content
... ... @@ -3,44 +3,36 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release contains multiple bug fixes, as well as some other improvements. The monitoring graphs have been improved, such that they can now show data up to the last thirty days. Moreover, we can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. Furthermore, several improvements regarding failover functionality have been done. Lastly, bug fixes regarding resource paths and image versions have been done.
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 -== **Feedback Items** ==
8 +== **Cloud Template R20 - Double Lane** ==
9 9  
10 -//__On premise Windows machines__//
11 -Support for deploying to on premise Windows machines has been delivered.
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 -//__Adding multiple attributes__//
14 -It is now possible to add multiple existing attributes to an entity at once.
12 +== **Cloud Template R27 - Single Lane** ==
15 15  
16 -//__Monitoring graphs__//
17 -The monitoring graphs can now show data up to the last thirty days.
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"]].
18 18  
19 -== **Bug Fixes** ==
20 -//__Image versions__//
21 -The deletion of releases with deployed container versions will not be blocked anymore. Automated release clean up behaviour will also not exclude these releases from deletion. Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases.
16 +== **Feedback Items** ==
22 22  
23 -//__Failover group helptext__//
24 -The helptext of the Group attribute has been improved.
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"]].
25 25  
26 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
21 +== **Bug Fixes** ==
27 27  
28 -//__Failover group refresh__//
29 -A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in Group tab of "Start/Stop Flows" screen.
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.
30 30  
31 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
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.
32 32  
33 -//__Resource paths__//
34 -After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed.
35 -
36 36  == **Fancy Forum Answers** ==
37 37  
38 38  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:
39 39  
40 -* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]]
41 -* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]]
42 -* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]]
43 -* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||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"]]
44 44  
45 45  == **Key Takeaways** ==
46 46