Changes for page 212 - Failover Fiesta

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

From 45.1 to 46.1 From 185.1 to 186.1

From version 46.1

edited by Erik Bakker
on 2022/11/21 12:31

Change comment: There is no comment for this version

To version 185.1

edited by Carlijn Kokkeler
on 2023/10/23 14:44

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 @@
--188 - Close Encounters
++207 - Aligned State

Author

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

Content

@@ -2,80 +2,100 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community.
++**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.
--== **3rd generation runtime bolstering** ==
++== **State Generation** ==
--This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it.
++//__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.
--//__Migration of JMS backup configuration improved__//
++//__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
--//__Prechecks on Upgrade option made available for 3rd generation runtime__//
--//__Autogenerated exits can be deployed at once__//
++== **Metrics Storage Duration** ==
++
++
++
--//__Code mapping functionality available on 3rd generation runtime__//
++== **Feedback Items** ==
--//__Improved the performance of deploying or activating a release__//
++//__Alerting manual pause__//
++A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
--//__Failing runtimes won't be restarted indefinetly anymore__//
++//__Ordering of graphs in Manage__//
++The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
--== **Exportable Release Audit** ~* ==
++//__UTC times in Grafana panels__//
++All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
--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.
++//__Update flow designer version__//
++The framework used in the flow designer has been updated, improving performance.
--[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
++//__Carwash track TLS versions in logging__//
++A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
--{{warning}}Note that the following restrictions apply when exporting an audit document:
--  * Changes made on definition and transformation level are **not** restored
--  * You will **not** be able to restore to any flow version that was created before October 17th, 2022
--  * 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
--  * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
++//__Moving channels in the flow designer__//
++Moving already attached channels in the flow designer has been made sligthly easier.
--== **Feedback items ** ==
++//__Topic sizes description change__//
++In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
--We have also solved other feedback items besides the flow designer's critical updates.
++//__Password change notification__//
++When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
--//__Data Sink Refactor__//
--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 your seperately.
++//__Password comparison__//
++When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
--//__Improved naming convention on Store related pages__//
--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.
++//__Inactive user alerting__//
++Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
--//__Press "Enter" to search on multiple pages__//
--In our Daemon Switch release we added functionality that allowed you to press **Enter** to search on the property overview page. With this release we have added this functionality to many more pages across the portal. The complete list is as follows
++//__Alphabetical sorting on user level in HTTP statistics__//
++Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
--* Deploy → Deployment Plan
--* Deploy → Properties → History
--* Deploy → User Management → Roles
--* Manage → Error Messages → Error Messages
--* Manage → Error Messages → Flows with Error Messages
--* Manage → Error Messages → Exceptions of Error Messages
--* Manage → Log Entries
--* Manage → Alerts
--* Manage → Triggers
--* Manage → Tags – Cant find (only Gen2)
--* Manage → Notifications
--* Manage → Notification Settings
--* Manage → Data Usage → History
--* Manage → Code mappings → All tabs
++== **Bug Fixes** ==
++
++//__Flow designer styling__//
++The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
++
++//__Partial search for messages__//
++It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
++
++//__Disk usage after cloud template update__//
++In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
++
++//__Error handling migration__//
++If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
++
  == **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:
--* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
--* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
--* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
--* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
++* [[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"]]
++
  == **Key takeaways** ==
--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:
++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:
  * 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
@@ -88,6 +88,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 GEN3-only feature.
++~*~* Indicates a next-generation-architecture only feature.
  {{/info}})))((({{toc/}}))){{/container}}
  {{/container}}

Changes for page 212 - Failover Fiesta

Summary

Details

Navigation