Skip to Content

Changes for page 214 - System Symphony

Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 156.1
edited by Carlijn Kokkeler
on 2023/10/10 13:56
Change comment: There is no comment for this version
To version 376.1
edited by Carlijn Kokkeler
on 2024/02/12 15:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +214 - System Symphony
Content
... ... @@ -1,54 +1,48 @@
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!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
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 30 days. Moreover, support for deploying to on premise Windows machines is now available. Furthermore, several improvements regarding failover functionality have been done. Lastly, bug fixes regarding resource paths and image versions have been done.
6 6  
7 -== **Deployment Plan** ==
8 +== **Feedback Items** ==
8 8  
9 -//__Improved deployment plan to make the process better and more predictable__//
10 -The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
10 +//__On premise Windows machines__//
11 +Support for deploying to on premise Windows machines has been delivered.
11 11  
12 -//__Editing release properties__//
13 -With this release, it will be possible to change the description of a property by editing the property.
13 +//__Adding multiple attributes__//
14 +It is now possible to add multiple existing attributes to an entity at once.
14 14  
15 -//__JMS memory setting check__//
16 -A change in memory settings triggers redeployment of the container now.
16 +//__Monitoring graphs__//
17 +The monitoring graphs can now show data up to the last 30 days.
17 17  
18 -//__Properties tab__//
19 -We have removed the deprecated tab Properties in the Deploy phase.
20 -
21 -//__Cleanup old images__//
22 -
23 -== **Store Improvements** ==
24 -
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.
25 25  
26 -== **Feedback Items** ==
23 +//__Failover group helptext__//
24 +The helptext of the Group attribute has been improved.
27 27  
28 -//__Alerting manual pause__//
29 -A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
26 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
30 30  
31 -//__Ordering of graphs in Manage__//
32 -The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
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.
33 33  
34 -//__UTC times in Grafana panels__//
35 -All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
31 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
36 36  
37 -//__Update flow designer version__//
38 -The framework used in the flow designer has been updated to the latest version.
33 +//__Resource paths__//
34 +After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed.
39 39  
40 -
41 -
42 -== **Bug Fixes** ==
43 -
44 -
45 45  == **Fancy Forum Answers** ==
46 46  
47 47  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:
48 48  
49 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
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"]]
50 50  
51 -== **Key takeaways** ==
45 +== **Key Takeaways** ==
52 52  
53 53  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:
54 54  
... ... @@ -59,7 +59,6 @@
59 59  * Check out the release notes [here]
60 60  * Start thinking about how the license tracker can aid your development
61 61  * Start thinking about major, minor, and patch
62 -* Upgrade to the latest build number
63 63  * Keep making great integrations
64 64  
65 65  Let's stay in touch and till next time!
... ... @@ -67,6 +67,11 @@
67 67  {{info}}
68 68  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
69 69  
70 -~*~* Indicates a next-generation-architecture only feature.
71 -{{/info}})))((({{toc/}}))){{/container}}
63 +{{/info}}
64 +)))
65 +
66 +(((
67 +{{toc/}}
68 +)))
72 72  {{/container}}
70 +{{/container}}