190 - Fast Forward

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

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. 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.

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 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.

Message Redelivery 

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).

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.

• 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.

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.

Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture
As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.

Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture
We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.

Correct property generation for Event Streaming flows using the 3rd generation runtime architecture
With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.

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:

• Is eMagiz able to read XSD attributes
• Does eMagiz use ActiveMQ?
• Tool for test messages to eMagiz Queues
• How to Remove Cloud Container

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:

• If you have questions surrounding our Program Increment Planning, please get in touch with productmanagement@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) 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
• 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!