Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 103.1
edited by Erik Bakker
on 2023/08/29 11:07
Change comment: There is no comment for this version
To version 84.1
edited by Erik Bakker
on 2023/05/26 08:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -204 - Found It
1 +198 - Great Migration
Content
... ... @@ -1,18 +1,23 @@
1 -In the last sprint cycle, we focused on the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact.
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.204 - Found It.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 5  =====Minor changes=====
6 6  
7 -* Deploy - Containers: Removed generation of unnecessary properties from the 3rd generation event streaming containers.
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: When pressing "Apply to Environment" in Deploy -> Architecture there is no hard dependencies anymore on the (active) release when running in the next generation architecture. This makes it more clear and tangible what function is necessary for what goal.
13 +* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
14 +* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
8 8  
9 9  ====Bug fixes====
10 10  
11 -* Deploy - Releases: Container images are rebuilt correctly after changing a container’s IaaS. (#970)
12 -* Manage - Error messages: Error messages with a lengthy message history will also be displayed. This change only impacts containers that work on the 3rd generation architecture.
13 -* Deploy - Releases: When a user activates a release containing nested properties and the property is not created, we show it now as missing. We add the property placeholder after the user tries to activate the release.
14 -* Manage - Error messages: Error messages with a stack trace larger than 32kb will also be displayed. This change only impacts containers that work on the 3rd generation architecture.
18 +* 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.
19 +* 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.
15 15  
16 -=====Infra and image changes=====
21 +====Remarks====
17 17  
18 -* Image: A fix is released with this new image to ensure that specific error messages (see above) will also be displayed in Manage.
23 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.