Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 443.1
edited by Carlijn Kokkeler
on 2024/04/08 12:51
Change comment: There is no comment for this version
To version 280.1
edited by Carlijn Kokkeler
on 2023/12/04 15:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -218 - Sprightly Spring
1 +209 - Deployment Delights
Content
... ... @@ -3,44 +3,56 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
6 +**Hi there, eMagiz developers!** We have...
7 7  
8 +== **Release Maintenance** ==
8 8  
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 -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
22 22  
23 -Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
24 24  
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"]].
26 26  
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"]].
28 -
29 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.
32 32  
33 -//__Root Cloud__//
34 -Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
16 +//__Container version overview__//
17 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
35 35  
19 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
20 +
21 +//__Unchanged containers__//
22 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
23 +
24 +//__Rebuilding of images__//
25 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
26 +
27 +
28 +== **Bug Fixes** ==
29 +
30 +//__Runtime metrics processing__//
31 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
32 +
33 +//__Deployment plan__//
34 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
35 +
36 +//__Store message merging__//
37 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
38 +
39 +//__View all store items__//
40 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
41 +
42 +//__Out of memory behavior__//
43 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
44 +
45 +//__Max fetch size__//
46 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
47 +
48 +
36 36  == **Fancy Forum Answers** ==
37 37  
38 38  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:
39 39  
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"]]
53 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
42 42  
43 -== **Key Takeaways** ==
55 +== **Key takeaways** ==
44 44  
45 45  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:
46 46  
... ... @@ -51,6 +51,7 @@
51 51  * Check out the release notes [here]
52 52  * Start thinking about how the license tracker can aid your development
53 53  * Start thinking about major, minor, and patch
66 +* Upgrade to the latest build number
54 54  * Keep making great integrations
55 55  
56 56  Let's stay in touch and till next time!
... ... @@ -58,6 +58,7 @@
58 58  {{info}}
59 59  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
60 60  
74 +~*~* Indicates a next-generation-architecture only feature.
61 61  {{/info}}
62 62  )))
63 63