Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 460.1
edited by CarlijnKokkeler
on 2024/04/10 11:56
Change comment: There is no comment for this version
To version 196.1
edited by CarlijnKokkeler
on 2023/10/23 15:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -218 - Sprightly Spring
1 +207 - Aligned State
Content
... ... @@ -1,48 +1,77 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we will do a large maintenance update, moving the eMagiz [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] stack from Spring 5 to Spring 6 and from Java 8 to Java 17. Please refer to our new [[runtime image>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]] and Spring 6 [[migration path>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]] for more information. Next to this, we have improved event streaming logging, so that logs are not cluttered with irrelevant info anymore. Lastly, we have removed the deprecated cloud option 'Root' from the portal.
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. State generation functionality is only accessible for models with an add-on state generation license. 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.
7 7  
8 -== **Spring 6 Migration** ==
9 -As announced in our previous release blogs, we will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture in this release.
7 +== **State Generation** ==
10 10  
11 -Configurations that contain any one of the listed components below are automatically migrated to Spring 6:
12 -* JDBC BoneCP data source
13 -* SSL web service message sender
14 -* Web service outbound gateway
15 -* SFTP session factory
16 -* HTTP components message sender
17 -* Job manager
18 -* Credentials
19 -* Simple job launcher
20 -* Default SFTP session factory
9 +//__New components__//
10 +The following components have been added:
11 +* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
12 +* Infinispan metadata outbound channel adapter: used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
13 +* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
14 +* Duplicate detector: support object used to detect duplicate messages for a certain key on an inbound channel of a flow component. Duplicates can be marked or discarded.
15 +* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.
21 21  
22 -{{info}}In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]].
17 +//__SpEL functions & JSON__//
18 +Added SpEL functions for:
19 +* Encoding & decoding Base64, Hex and hmac.
20 +* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
21 +* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).
23 23  
24 -This large maintenance update, moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]]. {{/info}}
23 +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`.
25 25  
26 -{{info}}Please be aware that we will create autosaved versions for affected flows still running on the legacy runtime architecture. This way, we ensure consistency in what the user sees when working with flow components in the Create phase while at the same time prepare your model for a future migration to the current runtime architecture. Should you need to make a functional change in one of these affected flows, you can do so without a deployment and without using Spring 6 in your legacy runtime. {{/info}}
25 +Added support for `#JsonPath` usage in SpEL expressions.
27 27  
27 +//__New image version 2.0.0__//
28 +The above functionalities are features of the new image version 2.0.0. Important to note is that the library used for Code Mappings has been changed. Changed the library used for Code Mappings. Any customer with Gen3 runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0.
29 +
30 +//__Component pages__//
31 +Pages to add the new components have been created. Forms have been created nicely with proper help texts. The EHCache cache manager has been removed.
32 +
33 +== **Metrics Storage Duration** ==
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 5, 7 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 +
36 +[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
37 +
28 28  == **Feedback Items** ==
29 -//__Event streaming logging__//
30 -Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs.
31 31  
32 -//__Root Cloud__//
33 -Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
40 +//__Import from store__//
41 +The button 'Import from Store' in Design will directly open the store instead of showing a pop asking whether the store should be opened.
34 34  
43 +//__Save and cancel buttons placement__//
44 +The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
45 +
46 +//__User session times__//
47 +The user session times for 3rd generation runtime dashboards have been extended, so that the user is not thrown out of the model when using the Manage phase for longer than an hour.
48 +
49 +//__Cancel and next buttons order//
50 +The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
51 +
52 +
53 +== **Bug Fixes** ==
54 +//__Topic and event-processor names__//
55 +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.
56 +
57 +//__System alignment__//
58 +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.
59 +
60 +
61 +
35 35  == **Fancy Forum Answers** ==
36 36  
37 37  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:
38 38  
39 -* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]]
40 -* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]]
41 -* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]]
42 -* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]]
66 +* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
67 +* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
68 +* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
69 +* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
70 +* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
43 43  
44 -== **Key Takeaways** ==
45 45  
73 +== **Key takeaways** ==
74 +
46 46  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
47 47  
48 48  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -52,6 +52,7 @@
52 52  * Check out the release notes [here]
53 53  * Start thinking about how the license tracker can aid your development
54 54  * Start thinking about major, minor, and patch
84 +* Upgrade to the latest build number
55 55  * Keep making great integrations
56 56  
57 57  Let's stay in touch and till next time!
... ... @@ -59,11 +59,6 @@
59 59  {{info}}
60 60  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61 61  
62 -{{/info}}
63 -)))
64 -
65 -(((
66 -{{toc/}}
67 -)))
92 +~*~* Indicates a next-generation-architecture only feature.
93 +{{/info}})))((({{toc/}}))){{/container}}
68 68  {{/container}}
69 -{{/container}}