Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/06/02 09:33
From version 239.1
edited by Erik Bakker
on 2025/04/07 09:25
Change comment: There is no comment for this version
To version 83.1
edited by Erik Bakker
on 2023/05/22 15:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -242 - Stability Score
1 +198 - Great Migration
Content
... ... @@ -1,18 +1,24 @@
1 -In the last sprint, we have released several items improving the stability of the platform across the various ILM phases. The biggest change we have is a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] allowing models running on our current-generation architecture to better utilize their CPU within the cloud models. On top of that, we release various improvements in the platform regarding clarity and stability.
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.242 - Stability Score.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====
5 +=====Minor changes=====
6 6  
7 -* Cloud - Templates: We have implemented a feature for Cloud models to be able to consume an unlimited amount of CPU burst on their production environment. This is released as part of a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||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: 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.
8 8  
9 -====Minor Changes====
10 -
11 -* Store - Overview: Statistics tab in Store item details shows the number of imports and the models where a store item has been imported to, which is only visible to store admins. (#799)
12 -* eMagiz Connector - Softcrow: Softcrow restoration is added for the eMagiz Connector.
13 -
14 14  ====Bug fixes====
15 15  
16 -* Create - Transformation: In the Transformation tab of the Create phase. Newly created attribute operations of type aggregator can freely switch positions with a destination filter using the move left or move right buttons. (#1307)
17 -* Create - Flow Designer: Updated help texts and documentation references that pointed to Joda time with the relevant Java DateTimeFormatter options to reflect the current state of libraries supported in the runtime images.
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.
18 18  
22 +====Remarks====
23 +
24 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.