Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-199 - Home Improvements
	1	+218 - Sprightly Spring

Author

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

Content

...	...	@@ -1,58 +1,56 @@
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 improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
	6	+**Hi there, eMagiz developers!**
6	6
7		-== **Next generation improvements and bug fixes** ==
8	8
9		-//__Enhanced overview of the HTTP Statistics__//
10		-As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
	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		-//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13		-In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
	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
14	14
15		-{{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}}
	23	+Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
16	16
17		-//__Forced congestion control__//
18		-To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
	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"]].
19	19
	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 [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] 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 [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]].
20	20
21		-//__Improved validation errors on the invalid configuration of HTTP outbound components__//
22		-This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
	29	+== **Feedback Items** ==
	30	+//__Event streaming logging__//
	31	+* Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs.
23	23
24		-//__Improved migration behavior__//
25		-This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
26		-A smoother migration of your JMS (and backup JMS) process.
27		-Shortening of names that otherwise would be too long, additional feedback given to the user.
28		-Feedback when the migration process is finished.
	33	+//__Root Cloud__//
	34	+Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
29	29
30		-//__Additional checks when deploying__//
31		-This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
32		-
33		-== **Store Improvements** ==
34		-
35		-== **Event Streaming - Certificate Management** ==
36		-
37	37	== **Fancy Forum Answers** ==
38	38
39	39	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:
40	40
41		-* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
42		-* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
	40	+* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
	41	+* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
43	43
44		-== **Key takeaways** ==
	43	+== **Key Takeaways** ==
45	45
46		-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:
	45	+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:
47	47
48	48	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
49	49	* If you have feedback or ideas for us, talk to the Platypus
50		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	49	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
51	51	* Clear your browser cache (Ctrl + Shift + Del)
52	52	* Check out the release notes [here]
53	53	* Start thinking about how the license tracker can aid your development
54	54	* Start thinking about major, minor, and patch
55		-* Upgrade to the latest build number
56	56	* Keep making great integrations
57	57
58	58	Let's stay in touch and till next time!
...	...	@@ -60,6 +60,11 @@
60	60	{{info}}
61	61	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
62	62
63		-~*~* Indicates a GEN3-only feature.
64		-{{/info}})))((({{toc/}}))){{/container}}
	61	+{{/info}}
	62	+)))
	63	+
	64	+(((
	65	+{{toc/}}
	66	+)))
65	65	{{/container}}
	68	+{{/container}}