Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 392.1
edited by Carlijn Kokkeler
on 2024/02/16 12:08
on 2024/02/16 12:08
Change comment:
There is no comment for this version
To version 444.1
edited by Carlijn Kokkeler
on 2024/04/08 12:51
on 2024/04/08 12:51
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -21 4- SystemSymphony1 +218 - Sprightly Spring - Content
-
... ... @@ -3,52 +3,42 @@ 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!** 7 7 8 -== **Feedback Items** == 9 9 10 - //__Onpremise Windowsmachines__//11 - Wecan nowdeployonWindows withoutrelyingon aLinuxsubsystem(WSL) tomake on-premise deploymentWindows hostmore accessible.9 +== **Spring 6 Migration** == 10 +As announced in our previous release blogs, we will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture in our release that will be released on April 11th, 2024, which is this release. 12 12 13 -[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]] 14 - [[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-windows.png]] 12 +Configurations that contain any one of the listed components below are automatically migrated to Spring 6: 13 +* JDBC BoneCP data source 14 +* SSL web service message sender 15 +* Web service outbound gateway 16 +* SFTP session factory 17 +* HTTP components message sender 18 +* Job manager 19 +* Credentials 20 +* Simple job launcher 21 +* Default SFTP session factory 15 15 16 -//__Adding multiple attributes__// 17 -It is now possible to add multiple existing attributes to an entity at once. This saves time when having to add multiple attributes to an entity. 23 +Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change. 18 18 19 - [[image:Main.Images.ReleaseBlog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]]25 +In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]]. 20 20 21 -//__Monitoring graphs__// 22 -The monitoring graphs can now show data up to the last thirty days. 27 +This large maintenance update, moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]]. 23 23 24 -== **Bug Fixes** == 25 -//__Image versions__// 26 -To keep the overview of releases compact we now have improved the (automatic) deletion behavior in the following way: 27 -* The deletion of releases with deployed container versions will not be blocked anymore. 28 -* Automated release clean up behaviour will also not exclude these releases from deletion. 29 -* 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. 29 +== **Feedback Items** == 30 +//__Event streaming logging__// 31 +Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs. 30 30 31 -//__ Failover grouphelptext__//32 - ThehelptextoftheGroupattributehasbeenimproved.33 +//__Root Cloud__// 34 +Options and screens related to the deprecated cloud option 'Root' have been removed from the portal. 33 33 34 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]] 35 - 36 -//__Failover group refresh__// 37 -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 the Group tab of "Start/Stop Flows" screen. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed. 38 - 39 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 40 - 41 -//__Resource paths__// 42 -After migrating a gateway away fom the legacy runtime architecture, the path references in the event processors would be broken. This has been fixed. 43 - 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 -* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]] 49 -* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]] 50 -* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]] 51 -* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||target="blank"]] 40 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 41 +* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]] 52 52 53 53 == **Key Takeaways** == 54 54