Changes for page 220 - Patch Parade

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-214 - System Symphony
	1	+198 - Great Migration

Author

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

Content

...	...	@@ -1,21 +1,24 @@
1		-In the last sprint cycle, we focused on improving failover aspects. Moreover, we improved the history of monitoring graphs, it is now possible to view data from up to the last 30 days. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
	1	+Another couple of weeks have passed, so it is time for a new release. We have focused in this period on improving the migration process towards the next-generation architecture as well as how the user experience and interaction with the next-generation architecture works.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.214 - System Symphony||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.198 - Great Migration.WebHome||target= "blank"]].
4	4
5		-=====New features=====
6		-
7		-* Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once.
8		-* Deploy - Architecture: Support for deploying to on premise Windows machines.
9		-
10	10	=====Minor changes=====
11	11
12		-* Deploy - Releases: Deletion of releases with deployed container versions will not be blocked anymore.
13		-* Manage - Monitoring: graphs can show last 30 days.
	7	+* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
	8	+* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
	9	+* Create - Flow designer: Added a validation for HTTP outbound gateways and HTTP outbound channel adapters that will create an alert if both Encoding mode and a REST template is set for the component.
	10	+* Deploy - Releases: We improved the performance of preparing and deploying releases, by optimizing the algorithm that decides if runtime images needs to be rebuild or not.
	11	+* Deploy - Releases: We improved resource validation when preparing releases. You will get notified when a flow resource was updated in one flow, but not in another flow in your release. Only applies to third generation runtimes.
	12	+* Deploy - Architecture: You can apply your changes to environment without having an active release.
	13	+* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
	14	+(control tower, so Gen3 only)
	15	+* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
14	14
15	15	====Bug fixes====
16	16
17		-* Create - Flow Designer: The help text of the Group attribute has been improved.
18		-* Create-Flowtesting: A bug fix has been done regarding resource paths that would change after running a flow test.
19		-* Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen.
	19	+* General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models.
	20	+* Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
20	20
	22	+====Remarks====
21	21
	24	+* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.