Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 199.1
edited by Carlijn Kokkeler
on 2023/10/23 16:15
Change comment: There is no comment for this version
To version 153.1
edited by Erik Bakker
on 2023/09/15 15:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +205 - World Explorers
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -2,113 +2,51 @@
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!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
6 6  
7 -== **State Generation** ==
7 +== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
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 +As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
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).
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`.
24 -
25 -Added support for `#JsonPath` usage in SpEL expressions.
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.
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 -
38 38  == **Feedback Items** ==
39 39  
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.
13 +//__Improved Validation when migrating to the next-generation architecture__//
14 +To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
42 42  
43 -//__Save and cancel buttons placement__//
44 -The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
16 +{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
45 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.
18 +//__Improved HTTP Statistics__//
19 +To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
48 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.
21 +//__Show values on the runtime level in Deploy Architecture__//
22 +We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
51 51  
52 -//__Data sink page__//
53 -The data sink page has been moved to the “Explore” tab.
24 +{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
25 +* JMS - The number of queues in the active release.
26 +* Messaging Container - The number of messaging integrations in the active release.
27 +* Messaging Connector - The number of messaging integrations related to this system in the active release.
28 +* API Gateway Container - The number of operations in the active release.
29 +* Event Streaming Container - The number of event processors in the active release.
54 54  
55 -//__Unused images removal__//
56 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
31 +There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
57 57  
58 -//__Flow Designer performance__//
59 -Performance improvements for the Flow Designer have been implemented.
60 -
61 -//__Properties with special characters__//
62 -When a user would migrate to gen3 and deploy their release containing properties with special characters, certain flows could not find the correct values to properties anymore or could not find the properties altogether. With this release, special characters such as a backslash do not break properties after deployment.
63 -
64 -//__Hidden flow fragements__//
65 -When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
66 -
67 -//__Resources disappearances__//
68 -Resources would disappear in the flow designer when pressing Cancel on selecting a new resource. With this release, resources without a name will not trigger error messages when users select components.
69 -
70 -//__Error channel for all inbounds__//
71 -If there is no custom error handling, Gen3 migration would set the error channel to “errorChannel” only for the first inbound in an entry flow.
72 -We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
73 -
74 -//__Highlighting resources__//
75 -The performance of highlighting resources of selected components is improved in Read only mode.
76 -
77 77  == **Bug Fixes** ==
78 78  
79 -//__Topic and event-processor names__//
80 -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.
35 +//__Gain the ability again to configure certificates in Deploy Architecture again__//
36 +In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
81 81  
82 -//__System alignment__//
83 -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.
38 +//__Ensure that differing container configurations deploy the correct configuration__//
39 +When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
84 84  
85 -//__Error checking__//
86 -Besides checking error header, the error trigger is now configured to check if an error message contains a term.
41 +//__Remove queurying options in Manage__//
42 +To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
87 87  
88 -//__Alerting__//
89 -For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
90 -For gen3 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%.
91 -The gen3 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.
92 -
93 -//__Unused containers__//
94 -Containers are set inactive when they are unused and removed in Design.
95 -
96 -//__Error popups when promoting a release version__//
97 -We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
98 -
99 -//__Memory leak__//
100 -A memory leak when using gen 3 metrics has been fixed.
101 -
102 102  == **Fancy Forum Answers** ==
103 103  
104 104  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:
105 105  
106 -* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
107 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
108 -* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
109 -* [[3rd generation runtime with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
48 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
110 110  
111 -
112 112  == **Key takeaways** ==
113 113  
114 114  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: