Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10

From 122.1 to 121.1 From 199.1 to 198.1

From version 198.1

edited by Carlijn Kokkeler
on 2023/10/23 16:10

Change comment: There is no comment for this version

To version 122.1

edited by Erik Bakker
on 2023/06/06 08:37

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--207 - Aligned State
++199 - Home Improvements

Author

@@ -1,1 +1,1 @@
--XWiki.CarlijnKokkeler
++XWiki.ebakker

Content

@@ -2,121 +2,56 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**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.
++**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
--== **State Generation** ==
++== **Next generation improvements and bug fixes** ==
--//__New components__//
--The following components have been added:
--* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
--* Infinispan metadata outbound channel adapter: used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
--* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
--* 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.
--* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.
++//__Enhanced overview of the HTTP Statistics__//
++As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
--//__SpEL functions & JSON__//
--Added SpEL functions for:
--* Encoding & decoding Base64, Hex and hmac.
--* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
--* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).
++//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
++In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
--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`.
++{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
--Added support for `#JsonPath` usage in SpEL expressions.
++//__Forced congestion control__//
++To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
--//__New image version 2.0.0__//
--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.
++//__Unused images are cleaned up__//
++This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan.
--//__Component pages__//
--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.
++//__Improved rollup and storage of metrics when running an event streaming solution__//
++To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
--== **Metrics Storage Duration** ==
--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.
++{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of July. From then on, all data before the 9th of June will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
--[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
++== **Store Improvements** ==
--== **Feedback Items** ==
++//__Improved importing behavior for specific use cases__//
++Before, it could happen that a certain placeholder that contained an asterisk were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users.
--//__Import from store__//
--The button 'Import from Store' in Design will directly open the store instead of showing a pop asking whether the store should be opened.
++//__Fixed bug in creating a message mapping on top of an imported system message__//
++It is now possbile to create a message mapping to an imported system message from the store.
--//__Save and cancel buttons placement__//
--The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
++== **Event Streaming - Certificate Management** ==
--//__User session times__//
--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.
++//__Expired certification notification__//
++As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
--//__Cancel and next buttons order__//
--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.
--
--//__Data sink page__//
--The data sink page has been moved to the “Explore” tab.
--
--//__Unused images removal__//
--When a release is removed, the related unused images in the on-premises machines will be removed as well.
--
--//__Flow Designer performance__//
--Performance improvements for the Flow Designer have been implemented.
--
--//__Properties with special characters__//
--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.
--
--//__Hidden flow fragements__//
--When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
--
--//__Resources disappearances__//
--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.
--
--//__Error channel for all inbounds__//
--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.
--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.
--
--//__Highlighting resources__//
--The performance of highlighting resources of selected components is improved in Read only mode.
--
--== **Bug Fixes** ==
--
--//__Topic and event-processor names__//
--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.
--
--//__System alignment__//
--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.
--
--//__Error checking__//
--Besides checking error header, the error trigger is now configured to check if an error message contains a term.
--
--//__Alerting__//
--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%.
--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%.
--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.
--
--//__Unused containers__//
--Containers are set inactive when they are unused and removed in Design.
--
--//__Error popups when promoting a release version__//
--We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
--
--//__Memory leak__//
--A memory leak when using gen 3 metrics has been fixed.
--
  == **Fancy Forum Answers** ==
  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:
--* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
--* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
--* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
--* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
--* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
++* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
++* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]]
--
  == **Key takeaways** ==
--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:
++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:
  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
  * If you have feedback or ideas for us, talk to the Platypus
--* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
++* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
  * Clear your browser cache (Ctrl + Shift + Del)
  * Check out the release notes [here]
  * Start thinking about how the license tracker can aid your development
@@ -129,6 +129,6 @@
  {{info}}
  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
--~*~* Indicates a next-generation-architecture only feature.
++~*~* Indicates a GEN3-only feature.
  {{/info}})))((({{toc/}}))){{/container}}
  {{/container}}

Changes for page 207 - Aligned State

Summary

Details

Navigation