Changes for page 224 - Summer Sonata

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -7,27 +7,36 @@
7	7
8	8
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	+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
	12	+== **Feedback Items** ==
	13	+//__Dynamic trigger__//
	14	+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.
22	22
23		-Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
	16	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
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"]].
	18	+//__Copy to clipboard buttons__//
	19	+Copy to clipboard buttons have been added to various pages:
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 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
	21	+ * Deploy agent pop-up
	22	+ * Create - Flow designer: Properties
	23	+ * Deploy - Property releases: Property details
28	28
29		-== **Feedback Items** ==
	25	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
30	30
	27	+//__Reset H2 database__//
	28	+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	+
	30	+{{info}}Please note the following:
	31	+
	32	+* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
	33	+* 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.
	34	+* For on-premise runtimes, only a reset of the runtime is needed.
	35	+
	36	+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}}
	37	+
	38	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
	39	+
31	31	== **Bug Fixes** ==
32	32	//__Runtime overview improvements__//
33	33	The runtime overview has been improved regarding checks on the runtime version.