Changes for page 194 - Giant Leap

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

From 80.1 to 79.1 From 85.1 to 84.1

From version 84.1

edited by Erik Bakker
on 2023/02/27 16:23

Change comment: There is no comment for this version

To version 80.1

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

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 @@
--193 - Fan Out
++191 - Fifty Fifty

Content

@@ -2,69 +2,136 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** In the last couple of weeks, we worked hard on API improvements and 3rd generation improvements for you all to see. Amongst the API improvements we now introduce the option to define REST/XML structures in your API gateway for your API callers to call. This brings more options to the user community in setting up the API Gateway structure in accordance with the needs and desires of the client. On top of that we have released several 3rd generation improvements. Amongst these we will add WS-Security functionality to the runtime and improvements on viewing release properties. Furthermore we have released new cloud templates to improve security in our current runtime and improve the auto-healing for 3rd generation runtime cloud slots. Last but not least we release the first adaptation of "State generation" that can be implemented with the help of us in your model. In the upcoming monts we will gather feedback from actual client cases and improve on this functionality.
++**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.
--== **REST XML for API Gateway** ~*~* ==
++== **Dynamic Alerts** ~*~* ==
--{{warning}}Note that a decision needs to be made to select XML or JSON as default format for all your operations hosted in your API Gateway.{{/warning}}
++{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
--To enhance your options when developing an API gateway that can be called by others we now introduce the option to select XML as the default message format on your API Gateway pattern. You can do this under Design -> Settings -> API Management. In here you can select and edit the settings.
++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.
--[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
++We offer alerting on five types.
--Every operation made after this decision will default to XML (or JSON which is still the default). Should you want to support JSON on some operations and XML on others you can select a default and manually correct the mediaType for the requests and responses to which it matters.
++* Error message
++* Log message
++* Queue consumers
++* Messages in queue
++* Queue throughput
--[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
--==**Cloud Template R23 - Single Lane** ==
++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.
--This release introduces a new cloud template for all our customers running in a single-lane setup in the 2nd generation runtime. This cloud template will update some specific security settings on these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
--==**Cloud Template R6 - Single Lane** ==
++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.
--This release introduces a new cloud template for all our customers running in a single-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
--==**Cloud Template R6 - Double Lane** ==
++== **Debugger ** ~*~* ~* ==
--This release introduces a new cloud template for all our customers running in a double-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
++{{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}}
--== **WS-Security on the 3rd generation runtime** ~*~* ==
++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.
--To further improve our offering on the 3rd generation runtime we now also have added the necessary functionality to allow you to call SOAP endpoints while utilizing WS-Security as well as securing your hosted SOAP endpoint through WS-Security protocols.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
--== **State Generation ~*~* ==
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
--With this release we introduce our first "State Generation" functionality to our user community. After rigorous internal testing and use we have now made a stride to also make it available to the user community on specific use case. In the following months we will gather feedback on this to further improve and release it in a simpler and more user friendly way to the user community.
++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.
--{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
++[[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 ** ==
--//__Removed OData as option for an API Gateway operation__//
--With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
++We have also solved other feedback items besides the flow designer's critical updates.
--//__Changes in API Gateway operation paths is automatically updated in Create__//
--When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
++//__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.
--{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
++//__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 ** ==
--//__Prevent endless loop in Deploy -> User Management__//
--With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
++//__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.
--{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
++//__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.
--//__Update error handling during migration to the 3rd generation runtime__//
--As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
++//__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:
--* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
--* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
--* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
++* [[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"]]
  == **Key takeaways** ==

Changes for page 194 - Giant Leap

Summary

Details

Navigation