Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 290.1
edited by Carlijn Kokkeler
on 2023/12/06 14:25
Change comment: There is no comment for this version
To version 195.1
edited by Carlijn Kokkeler
on 2023/10/23 15:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -210 - Deployment Delights
1 +207 - Aligned State
Content
... ... @@ -1,60 +1,66 @@
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 have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
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 -== **Alerts** ==
7 +== **State Generation** ==
9 9  
10 -//__Topic approaching max size alert__//
11 -The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
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.
12 12  
13 -//__Missing metrics alert__//
14 -We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
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).
15 15  
16 -== **Feedback Items** ==
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`.
17 17  
18 -//__Improved release build process__//
19 -When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
25 +Added support for `#JsonPath` usage in SpEL expressions.
20 20  
21 -//__Container version overview__//
22 -Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
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.
23 23  
24 -[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
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.
25 25  
26 -//_Improved deployment process_//
27 -The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
33 +== **Metrics Storage Duration** ==
34 +Manage - Monitoring: 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.
28 28  
29 -//__Rebuilding of images__//
30 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
36 +[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
31 31  
32 -== **Bug Fixes** ==
38 +== **Feedback Items** ==
33 33  
34 -//__Runtime metrics processing__//
35 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
40 +//__Import from store__//
41 +Design - Message Mapping: The button 'Import from Store' will directly open the store instead of showing a pop asking whether the store should be opened.
36 36  
37 -//__Deployment plan__//
38 -We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
43 +//__Save and cancel buttons__//
44 +The Save and Cancel buttons have been placed slightly further apart from each other to avoid misclicking.
39 39  
40 -//__View all store items__//
41 -An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
46 +//__User session times__//
47 +Manage - Monitoring: 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.
42 42  
43 -//__Out of memory behavior__//
44 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
49 +
45 45  
46 -//__Max fetch size__//
47 -In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
51 +== **Bug Fixes** ==
48 48  
53 +
54 +
49 49  == **Fancy Forum Answers** ==
50 50  
51 51  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:
52 52  
53 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
54 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
55 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
56 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
57 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
59 +* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
60 +* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
61 +* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
62 +* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
63 +* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
58 58  
59 59  
60 60  == **Key takeaways** ==
... ... @@ -77,11 +77,5 @@
77 77  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78 78  
79 79  ~*~* Indicates a next-generation-architecture only feature.
80 -{{/info}}
81 -)))
82 -
83 -(((
84 -{{toc/}}
85 -)))
86 +{{/info}})))((({{toc/}}))){{/container}}
86 86  {{/container}}
87 -{{/container}}