Wiki source code of 198 - Great Migration
Version 82.1 by Erik Bakker on 2023/05/22 15:19
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
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. |
| |
1.1 | 2 | |
| |
82.1 | 3 | Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.198 - Great Migration.WebHome||target= "blank"]]. |
| |
35.1 | 4 | |
| |
66.1 | 5 | =====New features===== |
| 6 | |||
| |
82.1 | 7 | |
| |
46.1 | 8 | =====Minor changes===== |
| |
37.1 | 9 | |
| |
82.1 | 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. | ||
| |
37.1 | 19 | |
| |
24.1 | 20 | ====Bug fixes==== |
| |
17.1 | 21 | |
| |
82.1 | 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. | ||
| |
80.1 | 24 | |
| 25 | ====Remarks==== | ||
| 26 | |||
| |
82.1 | 27 | * Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2. |