Changes for page 220 - Patch Parade
Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 219.1
edited by Carlijn Kokkeler
on 2024/04/08 14:57
on 2024/04/08 14:57
Change comment:
There is no comment for this version
To version 84.1
edited by Erik Bakker
on 2023/05/26 08:40
on 2023/05/26 08:40
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 218 -SprightlySpring1 +198 - Great Migration - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,13 +1,23 @@ 1 - Inlast sprintcycle, we focusedonreleasingamajorversionof our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]baseimage for allour clients running on the[[current runtime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]]architecture. Pleasereferto ournew[[runtime image>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]]and Spring 6 [[migration path>>doc:Main.eMagizSupport.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]] for moreinformation.Apart from this, wehave improved eventstreaminglogging,suchthattheselogsarenot cluttered with irrelevantinformationanymore. Moreover,wehaveremovedthedeprecated cloud option'Root' from theportal.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. 218 -SprightlySpring||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 -===== Newfeatures=====5 +=====Minor changes===== 6 6 7 -* Architecture: Several components are affected by the migration to Spring 6. Please check out our [[Release blog>>Main.Release Information.Release Blogs.218 - Sprightly Spring||target="blank"]] for specifications. 8 -* Architecture: 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"]]. 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. 9 9 10 -=====Minor changes===== 11 -* Manage - Monitoring: Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs. 12 -* Deploy - Cloud: Options and screens related to the deprecated cloud option 'Root' have been removed from the portal. 16 +====Bug fixes==== 13 13 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. 20 + 21 +====Remarks==== 22 + 23 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.