Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 119.1
edited by Erik Bakker
on 2023/06/05 14:27
Change comment: There is no comment for this version
To version 90.1
edited by Erik Bakker
on 2023/03/14 06:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -199 - Home Improvements
1 +194 - Big Leap
Content
... ... @@ -2,44 +2,66 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
5 +**Hi there, eMagiz developers!** In the last couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
6 6  
7 -== **Next generation improvements and bug fixes** ==
7 +== **3rd generation improvements** ==
8 8  
9 -//__Enhanced overview of the HTTP Statistics__//
10 -As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
9 +//__Better feedback in error log when a corrupt stylesheet is encountered__//
10 +We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
11 11  
12 -//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13 -In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
12 +//__Better internal error handling to avoid unnecessary alerting and notifications__//
13 +We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
14 14  
15 -{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
15 +//__Improved Manage Dashboard__//
16 +This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
16 16  
17 -//__Forced congestion control__//
18 -To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
18 +//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19 +When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes.
19 19  
21 +//__Improved process of deploy preparation__//
22 +With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
20 20  
21 -//__Improved validation errors on the invalid configuration of HTTP outbound components__//
22 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
24 +//__Improved migration of Streaming container__//
25 +When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
23 23  
24 -//__Improved migration behavior__//
25 -This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
26 -A smoother migration of your JMS (and backup JMS) process.
27 -Shortening of names that otherwise would be too long, additional feedback given to the user.
28 -Feedback when the migration process is finished.
27 +//__Add History to Notifications in Manage__//
28 +To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications.
29 29  
30 -//__Additional checks when deploying__//
31 -This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
30 +//__Improved Manage phase for Event Streaming__//
31 +Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you.
32 32  
33 -== **Store Improvements** ==
33 +//__Improved help text for network volumes__//
34 +With this release we have improved the help text that explains network volumes and how to use them within our solution.
34 34  
35 -== **Event Streaming - Certificate Management** ==
36 +{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]] on the subject.{{/warning}}
36 36  
38 +== **Feedback items ** ==
39 +
40 +//__Removed OData as option for an API Gateway operation__//
41 +With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
42 +
43 +//__Changes in API Gateway operation paths is automatically updated in Create__//
44 +When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
45 +
46 +{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
47 +
48 +== **Bug fixes ** ==
49 +
50 +//__Prevent endless loop in Deploy -> User Management__//
51 +With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
52 +
53 +{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
54 +
55 +//__Update error handling during migration to the 3rd generation runtime__//
56 +As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
57 +
37 37  == **Fancy Forum Answers** ==
38 38  
39 39  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
40 40  
41 -* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
42 -* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
62 +* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
63 +* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
64 +* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
43 43  
44 44  == **Key takeaways** ==
45 45