Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 331.1
edited by Carlijn Kokkeler
on 2024/01/03 09:09
Change comment: There is no comment for this version
To version 435.1
edited by Carlijn Kokkeler
on 2024/04/08 11:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +218 - Sprightly Spring
Content
... ... @@ -3,70 +3,67 @@
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 have done much work to improve our logging and overviews. This should improve the user experience for our platform. Next to this, we have done several minor changes and bug fixes, mainly relating to the Deploy and Manage phase.
6 +**Hi there, eMagiz developers!**
7 7  
8 -== **Logging** ==
9 -//__Missing log entries__//
10 -We improved crash handling so that log messages clearly show when and why a container failed to start.
11 11  
12 -//__Runtime logging__//
13 -We fixed a bug where no new log messages were showing up, even though they were produced by a container.
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.
14 14  
15 -//__Deployment execution error message__//
16 -In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
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
17 17  
18 -== **Overviews** ==
23 +Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
19 19  
20 -//__Runtime overview__//
21 -We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
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 runtime>>doc:Main.Support.Migration Paths.migration-path-spring-6-migration||target="blank"]].
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
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.
24 24  
25 -//__Missing properties overview__//
26 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
31 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
27 27  
28 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
33 +//__Copy to clipboard buttons__//
34 +Copy to clipboard buttons have been added to various pages:
29 29  
30 -//__Runtime restart or redeploy overview__//
31 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
36 + * Deploy agent pop-up
37 + * Create - Flow designer: Properties
38 + * Deploy - Property releases: Property details
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
40 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
34 34  
35 -== **Feedback Items** ==
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.
36 36  
37 -//__Breaking changes pop-up__//
38 -Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
45 +{{info}}Please note the following:
39 39  
40 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
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.
41 41  
42 -//__External recipients emailaddress__//
43 -The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
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}}
44 44  
45 -//__Broker queue metrics dashboards__//
46 -It is now possible to select the MQTT broker in the queue metrics dashboards.
53 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
47 47  
48 -//__Runtime image version__//
49 -The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
50 -
51 -
52 52  == **Bug Fixes** ==
56 +//__Runtime overview improvements__//
57 +The runtime overview has been improved regarding checks on the runtime version.
53 53  
54 -//__Message throughput__//
55 -The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
56 -
57 -//__Cloud template upgrade incorrect rollback__//
58 -An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
59 -
60 -//__Next generation block__//
61 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
62 -
63 63  == **Fancy Forum Answers** ==
64 64  
65 65  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:
66 66  
67 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||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"]]
68 68  
69 -== **Key takeaways** ==
66 +== **Key Takeaways** ==
70 70  
71 71  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:
72 72