Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 195.1
edited by Carlijn Kokkeler
on 2023/10/23 15:13
Change comment: There is no comment for this version
To version 47.1
edited by Erik Bakker
on 2022/11/21 13:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +188 - Close Encounters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -2,74 +2,85 @@
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. 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.
5 +**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
6 6  
7 -== **State Generation** ==
7 +== **3rd generation runtime bolstering** ==
8 8  
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.
9 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
16 16  
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).
11 +//__Migration of JMS backup configuration improved__//
12 +With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
22 22  
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`.
14 +//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 +As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
24 24  
25 -Added support for `#JsonPath` usage in SpEL expressions.
17 +//__Autogenerated exits can be deployed at once__//
18 +This release has fixed a bug that prevented you from deploying an exit flow correctly.
26 26  
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.
20 +//__Code mapping functionality available on 3rd generation runtime__//
21 +As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
29 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.
23 +//__Improved the performance when activating a release__//
24 +With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
32 32  
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.
26 +//__Failing runtimes won't be restarted indefinitely anymore__//
27 +We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
35 35  
36 -[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
29 +== **Exportable Release Audit** ~* ==
37 37  
38 -== **Feedback Items** ==
31 +On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
39 39  
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.
33 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
42 42  
43 -//__Save and cancel buttons__//
44 -The Save and Cancel buttons have been placed slightly further apart from each other to avoid misclicking.
35 +{{warning}}Note that the following restrictions apply when exporting an audit document:
36 + * Changes made on definition and transformation level are **not** restored
37 + * You will **not** be able to restore to any flow version that was created before October 17th, 2022
38 + * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
39 + * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
45 45  
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.
41 +== **Feedback items ** ==
48 48  
49 -
43 +We have also solved other feedback items besides the flow designer's critical updates.
50 50  
51 -== **Bug Fixes** ==
45 +//__Data Sink Refactor__//
46 +We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end, we will contact you separately.
52 52  
48 +//__Improved naming convention on Store related pages__//
49 +We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
53 53  
51 +//__Press "Enter" to search on multiple pages__//
52 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
54 54  
54 +* Deploy → Deployment Plan
55 +* Deploy → Properties → History
56 +* Deploy → User Management → Roles
57 +* Manage → Error Messages → Error Messages
58 +* Manage → Error Messages → Flows with Error Messages
59 +* Manage → Error Messages → Exceptions of Error Messages
60 +* Manage → Log Entries
61 +* Manage → Alerts
62 +* Manage → Triggers
63 +* Manage → Tags – Cant find (only Gen2)
64 +* Manage → Notifications
65 +* Manage → Notification Settings
66 +* Manage → Data Usage → History
67 +* Manage → Code mappings → All tabs
68 +
55 55  == **Fancy Forum Answers** ==
56 56  
57 57  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:
58 58  
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"]]
73 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
74 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
75 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
64 64  
65 -
66 66  == **Key takeaways** ==
67 67  
68 -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:
79 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
69 69  
70 70  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
71 71  * If you have feedback or ideas for us, talk to the Platypus
72 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
83 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
73 73  * Clear your browser cache (Ctrl + Shift + Del)
74 74  * Check out the release notes [here]
75 75  * Start thinking about how the license tracker can aid your development
... ... @@ -82,6 +82,6 @@
82 82  {{info}}
83 83  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
84 84  
85 -~*~* Indicates a next-generation-architecture only feature.
96 +~*~* Indicates a GEN3-only feature.
86 86  {{/info}})))((({{toc/}}))){{/container}}
87 87  {{/container}}