Changes for page 190 - Fast Forward

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

From 67.1 to 66.1 From 73.1 to 72.1

From version 72.1

edited by Erik Bakker
on 2023/01/19 09:02

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 (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -2,60 +2,54 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**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 and some minor enhancements. This release is characterized by the significant steps we took to release several major features on our 3rd generation runtime, including the queue browser and message redelivery functionality.
++**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.
--== **Queue Browser** ~*~* ==
++== **Queue Browser** ==
  {{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
--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.
++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.
--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.
++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@190-release-blog--queue-browser-overview.png]]
--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.
++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.
  * 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.
++  ** 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 specific message in the wiretap functionality, you can clear it from the overview so it does not clutter the view anymore
++  ** 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 displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
++  ** 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.
++  ** 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.
++  ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
  [[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]]
--{{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}}
++== **Message Redelivery ** ==
--== **Message Redelivery ** ~*~* ==
++{{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}}
--{{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}}
--
  [[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
--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).
++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).
--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.
++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.
--On top of that, we have added some additional functionality.
++On top of that we have added some additional functionality.
  * 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.
++  ** 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.
++  ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
  [[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
@@ -64,61 +64,61 @@
  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 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.
++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 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.
++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.
++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 used within eMagiz. This new setting will ensure the runtime controls when the H2 database is shut down.
++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 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.
++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 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"]]
++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"]]
--//__Performance improvement creating a release__//
--With this release, we have improved the performance of creating a release.
++//__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.
--//__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.
++//__Improved naming convention on Store related pages__//
++We have improved various display names using the merge functionality within our store offering.
--//__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.
++//__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 ** ==
--//__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.
++//__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.
--//__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.
++//__Incorrect resource locations__//
++We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
--//__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.
++//__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.
--//__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:
--* [[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"]]
++* [[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** ==

Changes for page 190 - Fast Forward

Summary

Details

Navigation