Changes for page 222 - Flee Frustration

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

From 67.1 to 66.1 From 487.1 to 486.1

From version 486.1

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

Change comment: There is no comment for this version

To version 67.1

edited by Erik Bakker
on 2023/01/18 10:25

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
++190 - Fast Forward

Author

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

Content

@@ -1,73 +1,131 @@
  {{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, the path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 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!** It has been a while since our last deployment on the 9th of December. As a result we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs as well as some small improvements. This release is characterized by the major steps we took to release several major features on our 3rd generation runtime among which are the queue browser and message redelivery functionality.
--== **Feedback Items** ==
++== **Queue Browser** ==
--//__eMagiz Mendix connector__//
--We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
++{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
--//__Improved OpenAPI import__//
--The path length in OpenAPI spec imports has been 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 the "Queue browser". You can access this functionality via the "Explore" menu option in Manage. With the help of the queue browser you can, as the name suggests, browse your queue.
--//__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.
++To do so, we offer two options within this functionality. 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 what data is currently present on the queue. When selecting the Wiretap functionality you automatically wiretap your queue and are presented with copies (on a special queue) of your actual message that pass through the queue from the moment you pressed the Wiretap button.
--[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
--{{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.
++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.
--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.
++* 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 inadvertedly put a lot of messages on a queue.
++* Clear message from the wiretap queue (Wiretap option)
++  ** Once you are done with the analysis of a certain 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 that are 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.
--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@190-release-blog--queue-browser-explore-overview.png]]
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.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.
++== **Message Redelivery ** ==
--//__Volume mapping passwords__//
--Passwords for network volumes are hidden on the machine after deployment.
++{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime and the functionality is enabled for you environment.{{/warning}}
--//__Create integration removal__//
--When removing an integration from Create, the Create phase is now correctly updated.
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
--//__Legacy statistics__//
--Legacy pages are now correctly hidden when running on the current runtime architecture.
++Just 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 as well under the "Explore" option in Manage. When selecting the message redelivery option you will see all messages that are currently in need to be redelivered (as an error occurred).
--//__Unused properties__//
--Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
++Just 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.
--//__Enumeration values__//
--Enumeration values for event processors can now be edited in Create.
++On top of that we have added some additional functionality.
--[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
++* 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.
--//__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.
++[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
++== **3rd generation runtime bolstering** ==
++
++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.
++
++//__Define memory settings for on-premise runtimes from Deploy Architecture__//
++With this release, you are now able to 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.
++
++//__Empty runtime feedback when deploying a release (or setting the release as active)__//
++To prevent that you are not being able to deploy a release to your environment due to a mismatch between what is in your release and in 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.
++
++//__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.
++
++//__Updated H2 database setting__//
++As of this release, we have improved the configuration of our H2 databases that are used within eMagiz. This new setting will ensure that the runtime controls when the H2 database is shut down.
++
++{{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}}
++
++//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
++As a replacement of the current HTTP settings context menu we have 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.
++
++//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
++With this release, we have added a context menu item that allows user to deploy the agent that is needed to run your 3rd generation architecture on-premise. For more information on how to install this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
++
++//__Added "Reset" functionality__//
++With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
++
++== **Feedback items ** ==
++
++We have also solved other feedback items besides the flow designer's critical updates.
++
++//__Improved naming convention on Store related pages__//
++We have improved various display names using the merge functionality within our store offering.
++
++//__Update security protocols for our internal architecture__//
++Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
++
++//__Improved read-only description for "if exists" constructions in Transformations__//
++To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
++
++
++== **Bug fixes ** ==
++
++//__Decent validation feedback when not filling in the property value__//
++We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
++
++//__Incorrect resource locations__//
++We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
++
++//__Apply to environment in User Management performance improvement__//
++We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
++
  == **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"]]
++* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
++* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
++* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
++* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||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!
@@ -75,11 +75,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