Changes for page 212 - Failover Fiesta

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

From 17.1 to 16.1 From 198.1 to 197.1

From version 197.1

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

Change comment: There is no comment for this version

To version 17.1

edited by eMagiz
on 2022/10/13 09:28

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
++185 - Get ready

Author

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

Content

@@ -2,121 +2,50 @@
  {{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!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
--== **State Generation** ==
++==**Audit trail User Management**==
++Since the introduction of the API Gateway and Event Streaming patterns in eMagiz, the notion of users and roles have been added to the platform. In the User Management section in Deploy you will find the overview of the users and roles configured in your model. With this release we have also added the history tab to this page in which the platform registers the changes made in Users & Roles. At the moment when the user presses the Apply to environment button, the changes between the previous history entry and this action are registered in this section. The popup that is displayed when pressing Apply to environment has been expanded with the list of entries that will be added to this History section.
++
++[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
--//__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.
--
--//__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).
--
--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`.
--
--Added support for `#JsonPath` usage in SpEL expressions.
--
--//__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.
--
--//__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.
--
--== **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.
--
--[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
--
--== **Feedback Items** ==
--
--//__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.
--
--//__Save and cancel buttons placement__//
--The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
--
--//__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.
--
--//__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.
--
++==**Next Generation Monitoring & Alerting engine**==
++In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now using State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations.
++
++* In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach).
++* We have also released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]].
++* In the new architecture all error messages are automatically send to the eMagiz monitoring & alerting stack, which means that these flow components are no longer required. During migration these will be removed. In case custom error handling is required, these components are made available in the Create Store and will point to the current error flow (which serves a new purpose from then onwards)
++* Hosted SOAP Webservices can be migrated to the new architecture which removes the need to use the Jetty component, and introduces the request layer as root element in the System Message. This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well.
++* The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms
++
++
++=== **Improvements** ===
++
++* Performance Deployment plan
++When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
++
++* Flow Designer updates
++We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
++
++[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
++
++* Store
++We have fixed several smaller Store import issues to improve the user experience.
++
  == **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:
++As always, a gentle reminder to all 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"]]
++* [[Start runtime via a delayed start in a Linux environment?>>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
++* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||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 help build, 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
@@ -123,12 +123,13 @@
  * Start thinking about major, minor, and patch
  * Upgrade to the latest build number
  * Keep making great integrations
++* Check out the new documentation portal.
  Let's stay in touch and till next time!
  {{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 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 212 - Failover Fiesta

Summary

Details

Navigation