Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31

From 78.1 to 77.1 From 488.1 to 487.1

From version 487.1

edited by CarlijnKokkeler
on 2024/04/23 15:25

Change comment: There is no comment for this version

To version 78.1

edited by Erik Bakker
on 2023/01/31 14: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 @@
--219 - Creation Carousel
++191 - Fifty Fifty

Author

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

Content

@@ -1,72 +1,151 @@
  {{container}}
--{{container layoutStyle="columns"}}
--(((
++{{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** This release, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, we have improved our functionality to enable users to seamlessly import OpenAPI specifications with URL paths of up to 300 characters in length. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published.
++**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.
--== **Feedback Items** ==
++== **Dynamic Alerts** ~*~* ==
--//__eMagiz Mendix connector__//
--We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
++{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
--//__Improved OpenAPI import__//
--The path length that eMagiz supports when importing OpenAPI specifications is now increased to a maximum of 300 characters.
++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 "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers on your environment. On the top of the list you will see all "static" alerts as defined by eMagiz. Below that you will see all "dynamic" alerts that you and your fellow teammembers (with sufficient rights) can view, edit and delete.
--//__Flow test stack trace__//
--If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab.
++We offer alerting on five types.
--[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
++* Error message
++* Log message
++* Queue consumers
++* Messages in queue
++* Queue throughput
--{{info}}With the release of Spring 6 in our previous release, some users reported that their filters have begun logging warnings about discarding messages even though the filter is configured to not throw an exception on rejection. For flows that process high numbers of messages (and potentially discard a lot of messages as well) this can significantly disturb the overview of the logs in the manage phase.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
--To mitigate this, you can change the filter that throws the warning so it specifically refers to a discard channel. Given the chosen configuration, we advice to use the nullChannel option. This will silently drop the message without registering a warning in the log. In case you find the warning in the log a nice addition, we suggest to add an explicit discard channel leading to a logging outbound channel adapter. This log component can then be configured to throw a warning.
++These five options give you the option to configure more or less the same as you are currently used to when configuring triggers. Once you make a choice for a type you can press the "Next" button to fill in the details of the trigger. One example of how this can look is shown below.
--In the next release, we will aid you by adding a validation check that will force you to select a discard channel when it is currently not selected once you edit the flow to create a new version. More on this in the next release blog. {{/info}}
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
--== **Bug Fixes** ==
--//__Error handling__//
--When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
++Once the trigger tab is filled in you can navigate to the "Output" tab to select the recipients for the trigger you are configuring. On top of that you can reduce the number of message at which congestion control is enabled if ten is too high for you.
--//__Volume mapping passwords__//
--Passwords for network volumes are now securely hidden in the runtime’s machine after deploying a new release.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
--//__Create integration removal__//
--When removing an integration from Create, the Create phase is now correctly updated.
++== **Debugger ** ~*~* ~* ==
--//__Legacy statistics__//
--Legacy pages are now correctly hidden when running on the current runtime architecture.
++{{warning}}Note that this functionality only works when the following criteria are met.
++* Your JMS server is running on the 3rd generation runtime
++* The store item called "3rd generation debugger" is imported in the infra flow of each runtime for which you want the ability to debug
++* A feature flag needs to be enabled on your model
++* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
--//__Unused properties__//
--Users should not be able to edit or delete eMagiz properties, and so these eMagiz properties will now not be shown in the 'Unused property overview' anymore.
++As with our current offering, we now offer a functionality with which you can debug channels and see them via the eMagiz portal. As stated above to get to this point you need to execute several steps to get your model ready to be "debugged". Once you have done this you can activate the "debug" mode, via Deploy -> Containers for **one** specific flow **per** runtime that is of particular interest to you. Once you have done this you will see a pop-up telling you whether the "debug" mode was indeed activated or not.
--//__Enumeration values__//
--Enumeration values for event processors can now be edited in Create.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
--[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
--//__SFTP sessions__//
--SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released.
++Assuming it was activated correctly you can navigate to Manage -> Explore -> Queue browser and select the emagiz.debug queue to see the messages coming through.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
++
++{{info}}Note the following limitations when working with the debugger.
++  * Your entire model needs to be migrated to the 3rd generation runtime
++  * Only **one** flow **per** runtime can be debugged **per** environment
++  * There is only **one** overview in which **all** debugged messages are shown
++  * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
++  * The debug 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 debug functionality will be shutdown automatically under water.
++    ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
++
++== **Volume mapping - Network Share** ==
++
++This release will introduce an additional functionality within our [[volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]] offering. With this additional configuration option you can configure a network share and configure it to create a mapping between a network share and a docker volume.
++
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
++
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
++
++== **Feedback items ** ==
++
++We have also solved other feedback items besides the flow designer's critical updates.
++
++//__Show status on machine level under Deploy Architecture__//
++With this release we are now able to show the status of the machine when opening the "Details" overview on machine level in Deploy -> Architecture.
++
++//__Improved validation feedback on non-supported WSS4J interceptor __//
++We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
++
++//__Improve help text in flow testing on Java classes__//
++We have improved the helptext when you are adding headers to your test message. In this helptext we explain the top five Java classes and how to note them down to make it work in the flow testing functionality and in eMagiz in general.
++
++//__Improved readibility of notification when trying to delete a runtime__//
++When you have forgotten one or more steps when deleting a runtime you will be notified by the system on this. With this release we have improved the readibility of the notification.
++
++//__Improved sorting of missing properties overview__//
++We have improved the sorting on the missing properties overview you will encounter when activating the "check properties" option.
++
++//__Improved notification when error message cannot be found__//
++We have improved the notification when an error message cannot be found from the message redelivery overview in our 3rd generation runtime.
++
++//__Additional lifecycle management overview__//
++We have added an additional lifecycle management overview to the portal in which users with enough permissions can get an overview of the lifecycle "state" of all customer models.
++
++//__Improved feedback when memory settings are negative__//
++We have added an additional check that validates whether memory settings on a specific container are of a negative value. In these cases you will be blocked from applying the changes to the environment as this won't lead to a working solution.
++
++//__Auto upgrade for a cloud template default to "ON"__//
++For each new cloud slot we will toggle the "automtatic cloud template update" to "Yes".
++
++//__Removed an irrelevant refresh button on a flow designer component__//
++We have removed an irrelevant refresh button on the standard filter component.
++
++//__Notification list shows all notifications on default__//
++When navigating to the Notification overview in Manage under Alerting you will now see all notifications instead of a filtered list on a specific state.
++
++== **Bug fixes ** ==
++
++//__Keep selection when copying properties__//
++We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
++
++//__Check on security header improved for API Gateway__//
++We improved the check in the API Gateway through which we validate whether an API caller is authenticated when using the API Key method to secure the API Gateway.
++
++//__Don't show systems with only "external" flows in Design__//
++We fixed a bug that caused systems to appear in Design in cases where there should be none.
++
++//__Fix styling of mendix login in some occurences__//
++When navigating to a specific URL the default Mendix login page would be shown. With this release we have fixed this behavior.
++
++//__Change timing of wake-up of cloud slots on Friday__//
++To prevent timing issues of waking up cloud slots on the Friday of our deployment we have changed the timing of when the cloud slots are woken up on Friday.
++
++//__Fixed a typo in the Topic statistics overview__//
++We fixed a typo in the topic statistics overview.
++
++//__Fixed a typo in the HTTP statistics overview__//
++We fixed a typo in the HTTP statistics overview.
++
++//__Activatation of release history when executing a deployment__//
++We ensured that the release history is activated when executing a deployment.
++
  == **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:
--* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
--* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
--* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
++* [[Characters transformed to � when retrieving from DataSink>>https://my.emagiz.com/p/question/172825635703287019||target="blank"]]
++* [[Can I test my API Gateway locally?>>https://my.emagiz.com/p/question/172825635703236592||target="blank"]]
++* [[Deploy stops when updating connector-infra>>https://my.emagiz.com/p/question/172825635703299903||target="blank"]]
--== **Key Takeaways** ==
++== **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>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
++* Check out the release notes [here]
  * Start thinking about how the license tracker can aid your development
  * Start thinking about major, minor, and patch
++* Upgrade to the latest build number
  * Keep making great integrations
  Let's stay in touch and till next time!
@@ -74,11 +74,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]]
--{{/info}}
--)))
--
--(((
--{{toc/}}
--)))
++~*~* Indicates a GEN3-only feature.
++{{/info}})))((({{toc/}}))){{/container}}
  {{/container}}
--{{/container}}

Changes for page 222 - Flee Frustration

Summary

Details

Navigation