Skip to Content

Changes for page 236 - Another Agent

Last modified by Erik Bakker on 2025/01/13 09:32
From version 174.1
edited by Carlijn Kokkeler
on 2023/12/21 16:18
Change comment: There is no comment for this version
To version 43.1
edited by Erik Bakker
on 2023/01/18 11:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +190 - Fast Forward
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,31 +1,32 @@
1 -In the last sprint cycle, we focused on improving several aspects related overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase.
1 +The release finished many new improvements to our 3rd generation runtime offering and fixed various annoying bugs and minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.190 - Fast Forward.WebHome||target="blank"]].
4 4  
5 5  =====New features=====
6 +* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
7 +* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your JMS server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime.
6 6  
7 -* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
8 -* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
9 +=====Major changes=====
9 9  
11 +* Manage - Redelivery: You can explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Besides that, you can also redeliver the message(s) on this page.
10 10  
11 -
12 -
13 -
14 14  =====Minor changes=====
15 15  
16 -* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
17 -* Deploy - Architecture: Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
18 -* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
15 +* Design - System message: 'Request' and 'Response' entities are automatically generated and set as root entities for new SOAP web service integrations in 3rd generation runtimes.
16 +* Create - Flow designer: sensitive information stored in property values is masked. (#790)
17 +* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so the user can use it to compare the previous versions.
18 +* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
19 +* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
20 +* Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828)
21 +* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
22 +* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
23 +* Deploy - Releases - You will be reminded of empty runtimes when activating a release. Empty runtimes are runtimes without flows in the release, and these runtimes should be removed from your architecture.
19 19  
20 -
21 -
22 -
23 -
24 24  ====Bug fixes====
26 +* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
27 +* Create - Flow Designer: When copying and pasting, support objects such as "property placeholder," "support.bus-connection-caching," and "support. bus-connection-plain" are not duplicated (#793)
28 +* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
29 +* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
30 +* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
31 +* Deploy - Architecture: The deploy runtimes option is only visible for admin. A new menu item, "Deploy agent," is added and visible for all users to show the command which can be used to deploy the agent to an on-premises machine.
25 25  
26 -* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.
27 -* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by the container.
28 -
29 -
30 -
31 -