Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 276.1
edited by Carlijn Kokkeler
on 2023/12/04 14:43
Change comment: There is no comment for this version
To version 439.1
edited by Carlijn Kokkeler
on 2024/04/08 11:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Deployment Delights
1 +218 - Sprightly Spring
Content
... ... @@ -3,46 +3,69 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have...
6 +**Hi there, eMagiz developers!**
7 7  
8 -== **Release Maintenance** ==
9 9  
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.
10 10  
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
11 11  
23 +Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
12 12  
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"]].
13 13  
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
28 +
14 14  == **Feedback Items** ==
30 +//__Dynamic trigger__//
31 +The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger.
15 15  
16 -//__Harbor port change__//
17 -The port for which you need to register has been changed ...?
33 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
18 18  
19 -//__Container version overview__//
20 -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 +//__Copy to clipboard buttons__//
36 +Copy to clipboard buttons have been added to various pages:
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
38 + * Deploy agent pop-up
39 + * Create - Flow designer: Properties
40 + * Deploy - Property releases: Property details
23 23  
24 -//__Unchanged containers__//
25 -When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
42 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
26 26  
27 -//__Rebuilding of images__//
28 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
44 +//__Reset H2 database__//
45 +For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines.
29 29  
47 +{{info}}Please note the following:
30 30  
31 -== **Bug Fixes** ==
49 +* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
50 +* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime.
51 +* For on-premise runtimes, only a reset of the runtime is needed.
32 32  
33 -//__Runtime metrics processing__//
34 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
53 +For more information please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]]{{/info}}
35 35  
36 -//__Deployment plan__//
37 -We solved a bug where a deployment step in the deployment plan could randomly get stuck.
55 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
38 38  
57 +== **Bug Fixes** ==
58 +//__Runtime overview improvements__//
59 +The runtime overview has been improved regarding checks on the runtime version.
60 +
39 39  == **Fancy Forum Answers** ==
40 40  
41 41  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:
42 42  
43 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
65 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
66 +* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
44 44  
45 -== **Key takeaways** ==
68 +== **Key Takeaways** ==
46 46  
47 47  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:
48 48  
... ... @@ -53,7 +53,6 @@
53 53  * Check out the release notes [here]
54 54  * Start thinking about how the license tracker can aid your development
55 55  * Start thinking about major, minor, and patch
56 -* Upgrade to the latest build number
57 57  * Keep making great integrations
58 58  
59 59  Let's stay in touch and till next time!
... ... @@ -61,7 +61,6 @@
61 61  {{info}}
62 62  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63 63  
64 -~*~* Indicates a next-generation-architecture only feature.
65 65  {{/info}}
66 66  )))
67 67