Changes for page 212 - Failover Fiesta

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

From 73.1 to 72.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 73.1

edited by Erik Bakker
on 2023/01/31 12:16

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
++191 - Fifty Fifty

Author

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

Content

@@ -2,121 +2,131 @@
  {{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 couple of weeks we had our quarterly "hackathon" in which we fixed a series of annoying bugs and introduced many small improvements. On top of that we also finished several additional features for our 3rd generation runtime that will make your life while running on the 3rd generation runtime easier and better manageable. Among the additional features we have the dynamic alerting and the debugger functionality.
--== **State Generation** ==
++== **Dynamic Alerts** ~*~* ==
--//__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.
++{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
--//__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).
++To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called the "Queue browser." You can access this functionality via the "Explore" menu in Manage. Then, with the help of the queue browser, you can browse your queue as the name suggests.
--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`.
++To do so, we offer two options within this functionality. First, we have the Explore function, and we have the Wiretap function. When selecting a queue and opting for the Explore option, you get a live view of the current data in the queue. Then, when choosing the Wiretap functionality, you automatically wiretap your queue and are presented with copies (on a particular queue) of your actual message that passes through the queue from the moment you press the Wiretap button.
--Added support for `#JsonPath` usage in SpEL expressions.
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
--//__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.
++After selecting the queue and choosing the option, eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option), or that passed the queue since the moment you activate the option (Wiretap option). For each message, you have various options at your disposal.
--//__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.
++* Delete the message from the queue (Explore option)
++  ** This means throwing away live data, which can be helpful in a test or acceptance environment where you inadvertently put many messages on a queue.
++* Clear message from the wiretap queue (Wiretap option)
++  ** Once you are done with the analysis of a specific message in the wiretap functionality, you can clear it from the overview so it does not clutter the view anymore
++* Refresh messages list (both options)
++  ** By pressing this button, you can refresh the list of messages displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
++* Save as test message
++  ** By pressing this button, you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so, we link the message to your model so you can still use it in the flow testing functionality.
++* Download
++  ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
--== **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@190-release-blog--queue-browser-explore-overview.png]]
--[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
--== **Feedback Items** ==
++{{info}}The following restrictions apply to this functionality:
++  * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
++  * The wiretap functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
++    ** After five minutes the wiretap functionality will be shutdown automatically under water.
++    ** To see new messages after the five minutes you will have to access the wiretap functionality again from scratch.{{/info}}
--//__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.
++== **Debugger ** ~*~* ~* ==
--//__Save and cancel buttons placement__//
--The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
++{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime, and the functionality is enabled for your environment.{{/warning}}
--//__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.
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
--//__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.
++As with our current offering, we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience, we have placed this functionality under the "Explore" option in Manage. When selecting the message redelivery option, you will see all messages that currently need to be redelivered (as an error occurred).
--//__Data sink page__//
--The data sink page has been moved to the “Explore” tab.
++As in the current functionality, you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that, you can still see the linked error message as you could before.
--//__Unused images removal__//
--When a release is removed, the related unused images in the on-premises machines will be removed as well.
++On top of that, we have added some additional functionality.
--//__Flow Designer performance__//
--Performance improvements for the Flow Designer have been implemented.
++* Search option
++  ** Original queue name
++  ** Original message ID (which can be found as a header called jms_messageid in the error message view)
++* Save as test message
++  ** By pressing this button, you can save the message and use it in our flow testing functionality in Create.
++* Download
++  ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
--//__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.
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
--//__Hidden flow fragements__//
--When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
++== **3rd generation runtime bolstering** ==
--//__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.
++This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
--//__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.
++//__Define memory settings for on-premise runtimes from Deploy Architecture__//
++With this release, you can now define the memory settings (and, therefore, the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases, you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes, you need to create a new release and deploy it to actualize the changes on-premise.
--//__Highlighting resources__//
--The performance of highlighting resources of selected components is improved in Read only mode.
++//__Empty runtime feedback when deploying a release (or setting the release as active)__//
++To prevent you are not being able to deploy a release to your environment due to a mismatch between what is in your release and Deploy Architecture, we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.
--== **Bug Fixes** ==
++//__Auto-fill namespaces for SOAP hosted webservices__//
++Based on your configuration in Design, eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages.
--//__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.
++//__Updated H2 database setting__//
++As of this release, we have improved the configuration of our H2 databases used within eMagiz. This new setting will ensure the runtime controls when the H2 database is shut down.
--//__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.
++{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}}
--//__Error checking__//
--Besides checking error header, the error trigger is now configured to check if an error message contains a term.
++//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
++As a replacement for the current HTTP settings context menu, we added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service), you now also can define whether the control bus needs to work for this runtime.
--//__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.
++//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
++With this release, we have added a context menu item allowing users to deploy the agent needed to run your 3rd generation architecture on-premise. For more information on installing this, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
--//__Unused containers__//
--Containers are set inactive when they are unused and removed in Design.
++//__Performance improvement creating a release__//
++With this release, we have improved the performance of creating a release.
--//__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.
++== **Feedback items ** ==
--//__Memory leak__//
--A memory leak when using gen 3 metrics has been fixed.
++We have also solved other feedback items besides the flow designer's critical updates.
++//__Sensitive information stored in properties is masked __//
++We have made how we display sensitive information across the portal similar for various parts of the portal.
++
++//__Importing "Private" store content to which you do not have access__//
++We have improved the user feedback a user will get when trying to import a "Private" store item unavailable to the user.
++
++
++== **Bug fixes ** ==
++
++//__Fix the possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
++We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
++
++//__Synchronization of Event Streaming topic states__//
++We fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
++
++//__Copy and paste default support objects__//
++With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow.
++
++//__Fix editability of properties when importing store items__//
++With this release, you can once again change property names upon importing a store item.
++
  == **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"]]
++* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
++* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
++* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
++* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||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 212 - Failover Fiesta

Summary

Details

Navigation