Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 347.1
edited by Carlijn Kokkeler
on 2024/01/17 09:55
Change comment: There is no comment for this version
To version 440.1
edited by Carlijn Kokkeler
on 2024/04/08 11:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +218 - Sprightly Spring
Content
... ... @@ -3,38 +3,43 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
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.
6 +**Hi there, eMagiz developers!**
7 7  
8 -== **Cloud Template R20 - Double Lane** ==
9 9  
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"]].
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.
11 11  
12 -== **Cloud Template R27 - Single Lane** ==
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
13 13  
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"]].
23 +Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
15 15  
16 -== **Feedback Items** ==
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"]].
17 17  
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"]].
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 image 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
20 20  
29 +== **Feedback Items** ==
30 +
21 21  == **Bug Fixes** ==
32 +//__Runtime overview improvements__//
33 +The runtime overview has been improved regarding checks on the runtime version.
22 22  
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.
25 -
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.
28 -
29 29  == **Fancy Forum Answers** ==
30 30  
31 31  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:
32 32  
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"]]
39 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
40 +* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
36 36  
37 -== **Key takeaways** ==
42 +== **Key Takeaways** ==
38 38  
39 39  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:
40 40