Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-218 - Sprightly Spring
	1	+211 - Log Luminary

Content

...	...	@@ -3,46 +3,70 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!**
7		-In this release, we will do a large maintenance update, moving the eMagiz [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] stack from Spring 5 to Spring 6 and from Java 8 to Java 17. Please refer to our new [[runtime image>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]] and Spring 6 [[migration path>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]] for more information. Next to this, we have improved event streaming logging, so that logs are not cluttered with irrelevant info anymore. Lastly, we have removed the deprecated cloud option 'Root' from the portal.
	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.
8	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 this release.
	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		-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	+//__Runtime logging__//
	13	+We fixed a bug where no new log messages were showing up, even though they were produced by a container.
22	22
23		-{{info}}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"]].
	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.
24	24
25		-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"]]. {{/info}}
	18	+== **Overviews** ==
26	26
27		-{{info}}Please be aware that we will create autosaved versions for affected flows still running on the legacy runtime architecture. This way, we ensure consistency in what the user sees when working with flow components in the Create phase while at the same time prepare your model for a future migration to the current runtime architecture. Should you need to make a functional change in one of these affected flows, you can do so without a deployment and without using Spring 6 in your legacy runtime. {{/info}}
	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.
28	28
	23	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
	24	+
	25	+//__Missing properties overview__//
	26	+The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
	27	+
	28	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
	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.
	32	+
	33	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
	34	+
29	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.
32	32
33		-//__Root Cloud__//
34		-Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
	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'.
35	35
	40	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
	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.
	44	+
	45	+//__Broker queue metrics dashboards__//
	46	+It is now possible to select the MQTT broker in the queue metrics dashboards.
	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	+== **Bug Fixes** ==
	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	+
36	36	== **Fancy Forum Answers** ==
37	37
38	38	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:
39	39
40		-* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]]
41		-* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]]
42		-* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]]
43		-* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]]
	67	+* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
44	44
45		-== **Key Takeaways** ==
	69	+== **Key takeaways** ==
46	46
47	47	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:
48	48