Changes for page 208 - Controlled State

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

From 16.1 to 17.1 From 75.1 to 76.1

From version 17.1

edited by eMagiz
on 2022/10/13 09:28

Change comment: There is no comment for this version

To version 75.1

edited by Erik Bakker
on 2023/01/31 13:02

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Title

@@ -1,1 +1,1 @@
--185 - Get ready
++191 - Fifty Fifty

Author

@@ -1,1 +1,1 @@
--XWiki.eMagiz
++XWiki.ebakker

Content

@@ -2,46 +2,106 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
++**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.
--==**Audit trail User Management**==
--Since the introduction of the API Gateway and Event Streaming patterns in eMagiz, the notion of users and roles have been added to the platform. In the User Management section in Deploy you will find the overview of the users and roles configured in your model. With this release we have also added the history tab to this page in which the platform registers the changes made in Users & Roles. At the moment when the user presses the Apply to environment button, the changes between the previous history entry and this action are registered in this section. The popup that is displayed when pressing Apply to environment has been expanded with the list of entries that will be added to this History section.
--
--[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
++== **Dynamic Alerts** ~*~* ==
--==**Next Generation Monitoring & Alerting engine**==
--In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now using State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations.
--
--* In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach).
--* We have also released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]].
--* In the new architecture all error messages are automatically send to the eMagiz monitoring & alerting stack, which means that these flow components are no longer required. During migration these will be removed. In case custom error handling is required, these components are made available in the Create Store and will point to the current error flow (which serves a new purpose from then onwards)
--* Hosted SOAP Webservices can be migrated to the new architecture which removes the need to use the Jetty component, and introduces the request layer as root element in the System Message. This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well.
--* The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms
--
--
--=== **Improvements** ===
--
--* Performance Deployment plan
--When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
--
--* Flow Designer updates
--We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
--
--[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
--
--* Store
--We have fixed several smaller Store import issues to improve the user experience.
--
++{{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 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
++
++[[image:Main.Images.Release Blog.WebHome@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.
++
++[[image:Main.Images.Release Blog.WebHome@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.
++
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
++
++== **Debugger ** ~*~* ~* ==
++
++{{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
++* The beta image is activated
++* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
++
++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.
++
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
++
++[[image:Main.Images.Release Blog.WebHome@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.
++
++[[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.
++
++//__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.
++
++== **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.
++
++//__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.
++
++//__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, a gentle reminder to all 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:
++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:
--* [[Start runtime via a delayed start in a Linux environment?>>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
--* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]
++* [[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"]]
  == **Key takeaways** ==
--Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
++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>>mailto:academy@emagiz.com]]
  * If you have feedback or ideas for us, talk to the Platypus
@@ -52,12 +52,11 @@
  * Start thinking about major, minor, and patch
  * Upgrade to the latest build number
  * Keep making great integrations
--* Check out the new documentation portal.
  Let's stay in touch and till next time!
  {{info}}
--~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
++~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
  ~*~* Indicates a GEN3-only feature.
  {{/info}})))((({{toc/}}))){{/container}}

Changes for page 208 - Controlled State

Summary

Details

Navigation