Skip to Content

Changes for page 224 - Summer Sonata

Last modified by dfirdausy on 2024/07/04 10:01
From version 127.1
edited by SametKaya
on 2023/06/20 13:14
Change comment: There is no comment for this version
To version 438.1
edited by CarlijnKokkeler
on 2024/04/08 11:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -200 - Uncharted Territories
1 +218 - Sprightly Spring
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.SametKaya
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,66 +1,79 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on a lot of things that are unfortunately not quite ready to be released. As a result the output of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **Next generation improvements and bug fixes** ==
8 8  
9 -//__Enhanced right-hand view within Deployment Plan context__//
10 -When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
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 -{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
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 -//__Improved timeout settings when deploying__//
15 -To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
23 +Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
16 16  
17 -{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
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"]].
18 18  
19 -//__Detailed HTTP Statistics now show user info in specific additional cases__//
20 -To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
27 +== **Feedback Items** ==
28 +//__Dynamic trigger__//
29 +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.
21 21  
22 -{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
31 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
23 23  
24 -//__Improved loading speed of Manage Dashboard__//
25 -This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
33 +//__Copy to clipboard buttons__//
34 +Copy to clipboard buttons have been added to various pages:
26 26  
27 -== **Store Improvements** ==
36 + * Deploy agent pop-up
37 + * Create - Flow designer: Properties
38 + * Deploy - Property releases: Property details
28 28  
29 -//__Importing in Design is improved__//
30 -We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
40 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
31 31  
32 -== **Bug Fixes** ==
42 +//__Reset H2 database__//
43 +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.
33 33  
34 -//__Deprecated reminder pop-up removed__//
35 -We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
45 +{{info}}Please note the following:
36 36  
37 -//__Improved selection area in Flow Designer__//
38 -When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow.
47 +* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
48 +* 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.
49 +* For on-premise runtimes, only a reset of the runtime is needed.
39 39  
40 -//__Improved Kafka settings__//
41 -For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
51 +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}}
42 42  
43 -{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
53 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
44 44  
55 +== **Bug Fixes** ==
56 +//__Runtime overview improvements__//
57 +The runtime overview has been improved regarding checks on the runtime version.
58 +
45 45  == **Fancy Forum Answers** ==
46 46  
47 47  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:
48 48  
49 -* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
50 -* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]]
63 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
64 +* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
51 51  
52 -== **Key takeaways** ==
66 +== **Key Takeaways** ==
53 53  
54 -Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
68 +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:
55 55  
56 56  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
57 57  * If you have feedback or ideas for us, talk to the Platypus
58 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
72 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
59 59  * Clear your browser cache (Ctrl + Shift + Del)
60 60  * Check out the release notes [here]
61 61  * Start thinking about how the license tracker can aid your development
62 62  * Start thinking about major, minor, and patch
63 -* Upgrade to the latest build number
64 64  * Keep making great integrations
65 65  
66 66  Let's stay in touch and till next time!
... ... @@ -68,6 +68,11 @@
68 68  {{info}}
69 69  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70 70  
71 -~*~* Indicates a GEN3-only feature.
72 -{{/info}})))((({{toc/}}))){{/container}}
84 +{{/info}}
85 +)))
86 +
87 +(((
88 +{{toc/}}
89 +)))
73 73  {{/container}}
91 +{{/container}}