Skip to Content

Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 234.1
edited by Carlijn Kokkeler
on 2023/10/25 14:19
Change comment: There is no comment for this version
To version 223.1
edited by Carlijn Kokkeler
on 2023/10/24 11:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,10 +2,12 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have done much work for state generation, so that you can derive more information from your data! Examples are enrichment, aggregation, change detection and duplicate detection. Next to state generation, several improvements regarding the alignment of components have been made. Moreover, performance improvements and bug fixes have been implemented. Lastly, a change in the metrics storage duration has been performed.
5 +**Hi there, eMagiz developers!** We have done much work for state generation, so that you can derive more information from your data! Examples are enrichment, aggregation, change detection and duplicate detection.
6 6  
7 7  {{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
8 8  
9 +Next to state generation, several improvements regarding the alignment of components have been made. Moreover, performance improvements and bug fixes have been implemented. Lastly, a change in the metrics storage duration has been performed.
10 +
9 9  == **State Generation~*~*** ==
10 10  
11 11  //__New components__//
... ... @@ -24,12 +24,10 @@
24 24  
25 25  Added support for SpEL property accessors for XML and JSON, meaning that you can read message payloads in SpEL expressions easily. For example, to retrieve the value for 'id' in the following JSON String: `{"id":"123"}`, this SpEL expression suffices: `payload.id`.
26 26  
27 -Added support for `#JsonPath` usage in SpEL expressions. With this functionality, you can access your JSON payloads in a similar way as you would access XML payloads using xPath.
29 +Added support for `#JsonPath` usage in SpEL expressions.
28 28  
29 29  {{info}}The components are all configurable from the Flow Designer in Create and are accompanied by a help text explaining the use cases and the various technical configurations. Note that to make the components work in your model, a new release containing the latest image (2.0.0) needs to be deployed.{{/info}}
30 30  
31 -{{warning}}The library used for Code Mappings has been changed. Any customer with next generation architecture runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0. This has no consequences on a functional level. {{/warning}}
32 -
33 33  == **Metrics Storage Duration** ==
34 34  We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 7, 14 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively.
35 35  
... ... @@ -84,16 +84,15 @@
84 84  The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
85 85  
86 86  //__System alignment__//
87 -The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases. This will be done for existing systems as well.
87 +The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases.
88 88  
89 -//__Error alerting__//
90 -The error trigger is now configured to check if an error message contains a certain term, besides checking the error header.
89 +//__Error checking__//
90 +Besides checking error header, the error trigger is now configured to check if an error message contains a term.
91 91  
92 92  //__Alerting__//
93 -For the next generation architecture models, several adaptations to triggers have been made.
94 -* For the next generation architecture models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
95 -* For the next generation architecture models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
96 -* The next generation architecture configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
93 +For the next generation architecture models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
94 +For the next generation architecture models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
95 +The next generation architecture configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
97 97  
98 98  //__Unused containers__//
99 99  Containers are set inactive when they are unused and removed in Design.