Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 86.1
edited by Erik Bakker
on 2023/06/05 16:04
Change comment: There is no comment for this version
To version 82.1
edited by Erik Bakker
on 2023/05/22 15:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -199 - Home Improvements
1 +198 - Great Migration
Content
... ... @@ -1,20 +1,26 @@
1 -In the last sprint cycle we have focused on improving various aspects of the portal functionality. Among others we focused on the next-generation architecture, the store, security and certificate management.
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.199 - Home Improvements.WebHome||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 +
5 5  =====Minor changes=====
6 6  
7 -* * Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
8 -* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately 3 months before the expiration dates of event streaming users' access certificates.
9 -* Deploy - Release: After successful machine deployments, unused runtime images will be automatically removed. This can be disabled by changing the machine step in your deployment plan.
10 -* Manage - Monitoring: HTTP statistics page now displays all of the resources.
11 -* Manage - Alerting: congestion control wil be enabled by default with 10 alerts per 10 minutes and user cannot see or change it.
12 -* General - Infra: Changed the library used for storing metadata in the eMagiz Control Tower.
10 +* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
11 +* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
12 +* 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.
13 +* 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.
14 +* 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.
15 +* Deploy - Architecture: You can apply your changes to environment without having an active release.
16 +* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
17 +(control tower, so Gen3 only)
18 +* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
13 13  
14 14  ====Bug fixes====
15 15  
16 -* Create - Store: Spring Reserved words that contain * are not incorrectly replaced with the prefix of the flow.
17 -* Manage - Monitoring: When an application failed to start, not all log messages were visible in the manage phase.
22 +* 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.
23 +* 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.
18 18  
19 19  ====Remarks====
20 20