Changes for page 214 - System Symphony
Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 152.1
edited by Erik Bakker
on 2023/09/15 08:37
on 2023/09/15 08:37
Change comment:
There is no comment for this version
To version 374.1
edited by Carlijn Kokkeler
on 2024/02/12 15:09
on 2024/02/12 15:09
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 -2 05-WorldExplorers1 +214 - System Symphony - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,53 +1,47 @@ 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!** We have processed additionalfeedback onthe Manage phase to ensure you can more easily create overviewsof yourstatistics, displaying all information correctly and improving themigration process to thenext-generation architecture in the Create phase slightly. On top of that,we have improved the scalability of our new generation monitoring stack and the alerting structure.We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.6 +**Hi there, eMagiz developers!** In this release, ... 6 6 7 -== ** Mandatory Cloud Template Upgrade - Next-generation models ** == 8 - 9 -As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains. 10 - 11 11 == **Feedback Items** == 12 12 13 -//__ ImprovedValidation whenmigrating tothe next-generation architecture__//14 - To improve the migrationprocesstothe next-generationarchitecture,wenowhowa list of all reported problems,allowing theuserto resolvethembeforemigratingto thenext-generation architecture.10 +//__Update flows__// 11 +Support for deploying to on premise Windows machines has been delivered. 15 15 16 -{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}} 13 +//__Image versions__// 14 +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. 17 17 18 -//__ ImprovedHTTP Statistics__//19 - To improvethefiltering and refreshfunctionalityweofferonthisoverview,we havemadeseveral changeshisreleasethat will improvethebehaviorofthisoverview.16 +//__Adding multiple attributes__// 17 +It is now possible to add multiple existing attributes to an entity at once. 20 20 21 -//__ Show values onheruntime level inDeploy Architecture__//22 - Wehaveimprovedthe values shownon theruntime (i.e.,container)level inDeployArchitecturesoyou can betterassesswhetherthememory configuration isstillsuitablefor yourdeployedsolution.19 +//__Monitoring graphs__// 20 +The monitoring graphs can now show data up to the last 30 days. 23 23 24 -{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence. 25 -* JMS - The number of queues in the active release. 26 -* Messaging Container - The number of messaging integrations in the active release. 27 -* Messaging Connector - The number of messaging integrations related to this system in the active release. 28 -* API Gateway Container - The number of operations in the active release. 29 -* Event Streaming Container - The number of event processors in the active release. 30 - 31 -There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}} 32 - 33 33 == **Bug Fixes** == 23 +//__Failover group helptext__// 24 +The helptext of the Group attribute has been improved. 34 34 35 -//__Gain the ability again to configure certificates in Deploy Architecture again__// 36 -In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture. 26 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]] 37 37 38 -//__ Ensure that differing containerconfigurations deploythe correct configuration__//39 - Whenyou runinamulti-runtimeconfigurationandchangethe actual flows that needtorunoncontainerA vs. container B, it happenedbeforethat all flows werestillbeing deployedonallruntimes. With thisrelease, we will feedthis informationcorrectly toourinfrastructuretoensurethe correctand configuredflowsaredeployed onthe proper containers.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. 40 40 41 -//__Remove queurying options in Manage__// 42 -To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors. 31 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 43 43 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 + 44 44 == **Fancy Forum Answers** == 45 45 46 46 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: 47 47 48 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||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"]] 49 49 50 -== **Key takeaways** ==44 +== **Key Takeaways** == 51 51 52 52 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: 53 53 ... ... @@ -58,7 +58,6 @@ 58 58 * Check out the release notes [here] 59 59 * Start thinking about how the license tracker can aid your development 60 60 * Start thinking about major, minor, and patch 61 -* Upgrade to the latest build number 62 62 * Keep making great integrations 63 63 64 64 Let's stay in touch and till next time! ... ... @@ -66,6 +66,11 @@ 66 66 {{info}} 67 67 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 68 68 69 -~*~* Indicates a next-generation-architecture only feature. 70 -{{/info}})))((({{toc/}}))){{/container}} 62 +{{/info}} 63 +))) 64 + 65 +((( 66 +{{toc/}} 67 +))) 71 71 {{/container}} 69 +{{/container}}