Changes for page 207 - Aligned State

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

From 79.1 to 80.1 From 124.1 to 125.1

From version 80.1

edited by Erik Bakker
on 2023/02/09 08:53

Change comment: There is no comment for this version

To version 124.1

edited by Erik Bakker
on 2023/06/19 14:21

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--191 - Fifty Fifty
++200 - Uncharted Territories

Content

@@ -2,136 +2,52 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@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.
++**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on a lot of things that are unfortanetly not quite ready to be released. As a result the ouput of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
--== **Dynamic Alerts** ~*~* ==
++== **Next generation improvements and bug fixes** ==
--{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
++//__Enhanced right-hand view within Deployment Plan context__//
++When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
--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.
++{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
--We offer alerting on five types.
++//__Improved timeout settings when deploying__//
++To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
--* Error message
--* Log message
--* Queue consumers
--* Messages in queue
--* Queue throughput
++{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
++//__Detailed HTTP Statistics now show user info in specific additional cases__//
++To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
--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.
++{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
++//__Improved loading speed of Manage Dashboard__//
++This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
--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.
++== **Store Improvements** ==
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
++//__Importing in Design is improved__//
++We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
--== **Debugger ** ~*~* ~* ==
++== **Bug Fixes** ==
--{{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 new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
++//__Deprecated reminder pop-up removed__//
++We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
--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.
++//__Improved selection area in Flow Designer__//
++When working on a large flow you can now select specific areas easily while you are scrolled down furhter down the flow.
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
++//__Improved Kafka settings_//
++For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
--[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
++{{info}}We stronly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
--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:
--* [[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"]]
++* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
++* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]]
  == **Key takeaways** ==

Changes for page 207 - Aligned State

Summary

Details

Navigation