Changes for page 214 - System Symphony
Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 119.1
edited by Erik Bakker
on 2023/06/05 14:27
on 2023/06/05 14:27
Change comment:
There is no comment for this version
To version 375.1
edited by Carlijn Kokkeler
on 2024/02/12 15:14
on 2024/02/12 15:14
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 99-HomeImprovements1 +214 - System Symphony - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,58 +1,57 @@ 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 thelastfewweeks, wehaveworkedhardonimproving various aspectsof ourhome.Amongotherswehave improved thelogging,alerting,andsecurityofurnext-generation architecture.Ontopofthat wehave improved theinnerworkingsofthestore andthecertificatemanagementfor thoseofus usingtheEvent Streamingpattern.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 -== ** Next generationimprovementsand bug fixes** ==8 +== **Feedback Items** == 8 8 9 -//__ Enhancedoverviewofthe HTTP Statistics__//10 - Asof now allresourcesthathave been called atleastoncesincedeploying them will nowshow up inthe left-bottom graph of theHTTP Statistics. This willmakeit easierto see whether a particular operationascalled within a timeframe. On top of thatit makes comparing data on various operationseasier. Inhere you can alsofilter on one (by pressing the+ icon)or moreby clicking on thefiltericon. In caseyou want to sort the table in adifferent manner you can click on the name of the column on which you want to sort.10 +//__On premise Windows machines__// 11 +Support for deploying to on premise Windows machines has been delivered. 11 11 12 -//__ Reasonwhy runtimecannotstartis now inthevast majority of cases reported back__//13 -I nthisrelease,wehave improvedthe way we reportfailuresduringstartup of runtimes.Thiswill ensurethatitecomes mucheasiertopinpointwhatwent wrong upon startup.13 +//__Adding multiple attributes__// 14 +It is now possible to add multiple existing attributes to an entity at once. 14 14 15 -{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 16 +//__Monitoring graphs__// 17 +The monitoring graphs can now show data up to the last 30 days. 16 16 17 -//__Forced congestion control__// 18 -To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform. 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. 19 19 23 +//__Failover group helptext__// 24 +The helptext of the Group attribute has been improved. 20 20 21 -//__Improved validation errors on the invalid configuration of HTTP outbound components__// 22 -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 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]] 23 23 24 -//__Improved migration behavior__// 25 -This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are: 26 -A smoother migration of your JMS (and backup JMS) process. 27 -Shortening of names that otherwise would be too long, additional feedback given to the user. 28 -Feedback when the migration process is finished. 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. 29 29 30 -//__Additional checks when deploying__// 31 -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. 31 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 32 32 33 -== **Store Improvements** == 33 +//__Resource paths__// 34 +After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed. 34 34 35 -== **Event Streaming - Certificate Management** == 36 - 37 37 == **Fancy Forum Answers** == 38 38 39 39 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: 40 40 41 -* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]] 42 -* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]] 40 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]] 41 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]] 42 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]] 43 43 44 -== **Key takeaways** ==44 +== **Key Takeaways** == 45 45 46 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:46 +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: 47 47 48 48 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 49 49 * If you have feedback or ideas for us, talk to the Platypus 50 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 50 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 51 51 * Clear your browser cache (Ctrl + Shift + Del) 52 52 * Check out the release notes [here] 53 53 * Start thinking about how the license tracker can aid your development 54 54 * Start thinking about major, minor, and patch 55 -* Upgrade to the latest build number 56 56 * Keep making great integrations 57 57 58 58 Let's stay in touch and till next time! ... ... @@ -60,6 +60,11 @@ 60 60 {{info}} 61 61 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 62 62 63 -~*~* Indicates a GEN3-only feature. 64 -{{/info}})))((({{toc/}}))){{/container}} 62 +{{/info}} 63 +))) 64 + 65 +((( 66 +{{toc/}} 67 +))) 65 65 {{/container}} 69 +{{/container}}