Changes for page 213 - Joyful Journeys

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

From 88.1 to 89.1 From 187.1 to 188.1

From version 89.1

edited by Erik Bakker
on 2023/03/14 06:50

Change comment: There is no comment for this version

To version 187.1

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

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 @@
--194 - Big Leap
++207 - Aligned State

Author

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

Content

@@ -2,86 +2,101 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** In the last couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
++**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 improvements** ==
++== **State Generation** ==
--//__Better feedback in error log when a corrupt stylesheet is encountered__//
--We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
++//__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.
--//__Better internal error handling to avoid unnecessary alerting and notifications__//
--We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
++//__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)
--//__Improved Manage Dashboard__//
--This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
++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
--//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
--When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes.
--//__Improved process of deploy preparation__//
--With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
++== **Metrics Storage Duration** ==
++
++
++
--//__Improved migration of Streaming container__//
--When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
++== **Feedback Items** ==
--//__Add History to Notifications in Manage__//
--To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications.
++//__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.
--//__Improved Manage phase for Event Streaming__//
--Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you.
++//__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).
--//__Improved help text for network volumes__//
--With this release we have improved the help text that explains network volumes and how to use them within our solution.
++//__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.
++//__Update flow designer version__//
++The framework used in the flow designer has been updated, improving performance.
++//__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}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]] on the subject.{{/warning}}
++//__Moving channels in the flow designer__//
++Moving already attached channels in the flow designer has been made sligthly easier.
--== **WS-Security on the 3rd generation runtime** ~*~* ==
++//__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.
--To further improve our offering on the 3rd generation runtime we now also have added the necessary functionality to allow you to call SOAP endpoints while utilizing WS-Security as well as securing your hosted SOAP endpoint through WS-Security protocols. Please make sure to create a new release that will trigger the image creation process which will included this feature when necessary.
++//__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.
--== **State Generation ~*~* ==
++//__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.
--With this release we introduce our first "State Generation" functionality to our user community. After rigorous internal testing and use we have now made a stride to also make it available to the user community on specific use case. In the following months we will gather feedback on this to further improve and release it in a simpler and more user friendly way to the user community.
++//__Inactive user alerting__//
++Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
--{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
++//__Alphabetical sorting on user level in HTTP statistics__//
++Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
--== **Feedback items ** ==
--//__Removed OData as option for an API Gateway operation__//
--With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
++== **Bug Fixes** ==
--//__Changes in API Gateway operation paths is automatically updated in Create__//
--When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
++//__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.
--{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
++//__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".
--== **Bug fixes ** ==
++//__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.
--//__Prevent endless loop in Deploy -> User Management__//
--With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
++//__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.
--{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
--
--//__Update error handling during migration to the 3rd generation runtime__//
--As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
--
  == **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:
--* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
--* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
--* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||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
@@ -94,6 +94,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 213 - Joyful Journeys

Summary

Details

Navigation