191 - Fifty Fifty

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

release-blog-intro.png

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.

Dynamic Alerts **

Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime

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.

We offer alerting on five types.

  • Error message
  • Log message
  • Queue consumers
  • Messages in queue
  • Queue throughput

191-release-blog--dynamic-alert-trigger-options.png

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.

191-release-blog--dynamic-alert-trigger-input.png

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.

191-release-blog--dynamic-alert-trigger-output.png

Debugger  ** *

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 new release is created that includes the flow changes and this release is deployed to the environment(s)

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.

191-release-blog--debugger-action-success.png

191-release-blog--debugger-action-failure.png

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.

191-release-blog--debugger-output-queue-browser.png

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.

Volume mapping - Network Share

This release will introduce an additional functionality within our volume mapping 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.

191-release-blog--volume-mapping-network-share-overview.png

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:

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!

* Indicates a Beta feature. If you would like to get access to this beta feature, please contact productmanagement@emagiz.com

** Indicates a GEN3-only feature.