Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-204 - Found It
	1	+218 - Sprightly Spring

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,49 +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!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.
	6	+**Hi there, eMagiz developers!**
6	6
	8	+
	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	+
	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
	22	+
	23	+Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
	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 runtime>>doc:Main.Support.Migration Paths.migration-path-spring-6-migration||target="blank"]].
	26	+
7	7	== **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.
8	8
9		-//__Improved check on nested property placeholders__//
10		-To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing.
	31	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
11	11
12		-//__Removed outdated properties when deploying on the new generation architecture stack__//
13		-We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before in order to connect to a Kafka cluster but have become obsolete once you migrate.
	33	+//__Copy to clipboard buttons__//
	34	+Copy to clipboard buttons have been added to various pages:
14	14
15		-{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}
	36	+ * Deploy agent pop-up
	37	+ * Create - Flow designer: Properties
	38	+ * Deploy - Property releases: Property details
16	16
17		-//__Improved performance Manage Dashboards__//
18		-We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
	40	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
19	19
20		-== **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.
21	21
22		-//__Errors with long stack traces or long message histories will now also show in eMagiz__//
23		-We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s).
	45	+{{info}}Please note the following:
24	24
25		-//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__//
26		-We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration.
	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.
27	27
	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}}
	52	+
	53	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
	54	+
	55	+== **Bug Fixes** ==
	56	+//__Runtime overview improvements__//
	57	+The runtime overview has been improved regarding checks on the runtime version.
	58	+
28	28	== **Fancy Forum Answers** ==
29	29
30	30	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:
31	31
32		-* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]
33		-* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||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"]]
34	34
35		-== **Key takeaways** ==
	66	+== **Key Takeaways** ==
36	36
37	37	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:
38	38
39	39	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
40	40	* If you have feedback or ideas for us, talk to the Platypus
41		-* 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.
42	42	* Clear your browser cache (Ctrl + Shift + Del)
43	43	* Check out the release notes [here]
44	44	* Start thinking about how the license tracker can aid your development
45	45	* Start thinking about major, minor, and patch
46		-* Upgrade to the latest build number
47	47	* Keep making great integrations
48	48
49	49	Let's stay in touch and till next time!
...	...	@@ -51,6 +51,11 @@
51	51	{{info}}
52	52	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
53	53
54		-~*~* Indicates a next-generation-architecture only feature.
55		-{{/info}})))((({{toc/}}))){{/container}}
	84	+{{/info}}
	85	+)))
	86	+
	87	+(((
	88	+{{toc/}}
	89	+)))
56	56	{{/container}}
	91	+{{/container}}