Wiki source code of 198 - Great Migration

Version 83.1 by Erik Bakker on 2023/05/22 15:20

Hide last authors
Erik Bakker 82.1 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.
eMagiz 1.1 2
Erik Bakker 82.1 3 Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.198 - Great Migration.WebHome||target= "blank"]].
Erik Bakker 35.1 4
Erik Bakker 46.1 5 =====Minor changes=====
Erik Bakker 37.1 6
Erik Bakker 82.1 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.
Erik Bakker 37.1 16
Erik Bakker 24.1 17 ====Bug fixes====
Erik Bakker 17.1 18
Erik Bakker 82.1 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.
Erik Bakker 80.1 21
22 ====Remarks====
23
Erik Bakker 82.1 24 * Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.