Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 459.1
edited by Carlijn Kokkeler
on 2024/04/10 11:55
Change comment: There is no comment for this version
To version 291.1
edited by Carlijn Kokkeler
on 2023/12/06 14:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -218 - Sprightly Spring
1 +210 - Deployment Delights
Content
... ... @@ -3,46 +3,62 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we will do a large maintenance update, moving the eMagiz [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] stack from Spring 5 to Spring 6 and from Java 8 to Java 17. Please refer to our new [[runtime image>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]] and Spring 6 [[migration path>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]] for more information. Next to this, we have improved event streaming logging, so that logs are not cluttered with irrelevant info anymore. Lastly, we have removed the deprecated cloud option 'Root' from the portal.
6 +**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
7 7  
8 -== **Spring 6 Migration** ==
9 -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 this release.
8 +== **Alerts** ==
10 10  
11 -Configurations that contain any one of the listed components below are automatically migrated to Spring 6:
12 -* JDBC BoneCP data source
13 -* SSL web service message sender
14 -* Web service outbound gateway
15 -* SFTP session factory
16 -* HTTP components message sender
17 -* Job manager
18 -* Credentials
19 -* Simple job launcher
20 -* Default SFTP session factory
10 +//__Topic approaching max size alert__//
11 +The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
21 21  
22 -{{info}}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"]].
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
23 23  
24 -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 [[runtime image>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]]. {{/info}}
16 +== **Feedback Items** ==
25 25  
26 -{{info}}Please be aware that we will create autosaved versions for affected flows still running on the legacy runtime architecture. This way, we ensure consistency in what the user sees when working with flow components in the Create phase while at the same time prepare your model for a future migration to the current runtime architecture. Should you need to make a functional change in one of these affected flows, you can do so without a deployment and without using Spring 6 in your legacy runtime. {{/info}}
18 +//__Improved release build process__//
19 +When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
27 27  
28 -== **Feedback Items** ==
29 -//__Event streaming logging__//
30 -Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs.
21 +//__Container version overview__//
22 +Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
31 31  
32 -//__Root Cloud__//
33 -Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
24 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
34 34  
26 +//__Improved deployment process__//
27 +The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
28 +
29 +//__Rebuilding of images__//
30 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
31 +
32 +== **Bug Fixes** ==
33 +
34 +//__Runtime metrics processing__//
35 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
36 +
37 +//__Deployment plan__//
38 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
39 +
40 +//__View all store items__//
41 +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.
42 +
43 +//__Out of memory behavior__//
44 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
45 +
46 +//__Max fetch size__//
47 +In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
48 +
35 35  == **Fancy Forum Answers** ==
36 36  
37 37  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:
38 38  
39 -* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]]
40 -* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]]
41 -* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]]
42 -* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]]
53 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
54 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
55 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
56 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
57 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
43 43  
44 -== **Key Takeaways** ==
45 45  
60 +== **Key takeaways** ==
61 +
46 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]]
... ... @@ -52,6 +52,7 @@
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
71 +* Upgrade to the latest build number
55 55  * Keep making great integrations
56 56  
57 57  Let's stay in touch and till next time!
... ... @@ -59,6 +59,7 @@
59 59  {{info}}
60 60  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61 61  
79 +~*~* Indicates a next-generation-architecture only feature.
62 62  {{/info}}
63 63  )))
64 64