Skip to Content

Changes for page 194 - Giant Leap

Last modified by Carlijn Kokkeler on 2024/04/18 13:18
From version 75.1
edited by Erik Bakker
on 2023/01/31 13:02
Change comment: There is no comment for this version
To version 82.1
edited by Erik Bakker
on 2023/02/14 14:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +192 - Small Step
Content
... ... @@ -2,102 +2,56 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**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.
5 +**Hi there, eMagiz developers!** In the last couple of weeks we worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have a new event streaming graph and some updates to our platform in general.
6 6  
7 -== **Dynamic Alerts** ~*~* ==
7 +== **Start/Stop Flows** ~*~* ==
8 8  
9 9  {{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
10 10  
11 -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.
11 +To enhance the options you have when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows". You can access this functionality via the "Deploy Architecture" overview in Deploy. On runtime level you can open the context menu and select the option called "Start/Stop Flows".
12 12  
13 -We offer alerting on five types.
13 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
14 14  
15 -* Error message
16 -* Log message
17 -* Queue consumers
18 -* Messages in queue
19 -* Queue throughput
15 +After selecting the option eMagiz will open a pop-up in which you can stop and start the starting point of each flow that is deployed on that runtime. The effect of this is that no new messages will be processed by the flow but all remaining messages will still be processed by the flow after stopping the flow. To stop a flow you simply select a flow and press the Stop button. To start it again press Start.
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
17 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
22 22  
23 -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.
19 +{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
21 +== **Manage overview Event Streaming** ~*~* ==
26 26  
27 -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.
23 +To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaing statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, by clicking on the "Event streaing statistics" overview, you can see metadata information on all your topics. Among others you can see whether data is consumed, on which topic a lot of data is produced, and whether consumers are lagging in consuming data.
28 28  
29 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
25 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
30 30  
31 -== **Debugger ** ~*~* ~* ==
32 -
33 -{{warning}}Note that this functionality only works when the following criteria are met.
34 -* Your JMS server is running on the 3rd generation runtime
35 -* The store item called "3rd generation debugger" is imported in the infra flow of each runtime for which you want the ability to debug
36 -* The beta image is activated
37 -* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
38 -
39 -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.
40 -
41 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
42 -
43 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
44 -
45 -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.
46 -
47 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
48 -
49 -{{info}}Note the following limitations when working with the debugger.
50 - * Your entire model needs to be migrated to the 3rd generation runtime
51 - * Only **one** flow **per** runtime can be debugged **per** environment
52 - * There is only **one** overview in which **all** debugged messages are shown
53 - * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
54 - * The debug functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
55 - ** After five minutes the debug functionality will be shutdown automatically under water.
56 - ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
57 -
58 -== **Volume mapping - Network Share** ==
59 -
60 -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.
61 -
62 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
63 -
64 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
65 -
66 66  == **Feedback items ** ==
67 67  
68 68  We have also solved other feedback items besides the flow designer's critical updates.
69 69  
70 -//__Improved validation feedback on non-supported WSS4J interceptor __//
71 -We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
31 +//__Topic configuration calculation__//
32 +With this release we have simplified the configuration of settings on topic level to enforce certain best practices within the portal and at the same time make it easier to configure topics.
72 72  
73 -//__Improve help text in flow testing on Java classes__//
74 -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.
34 +//__Make preparation step in deployment plan visible__//
35 +For a deployment on the 3rd generation runtime to work some preparation work needs to be done by the portal. We have now made this step explicit and part of the deployment plan.
75 75  
76 -//__Improved readibility of notification when trying to delete a runtime__//
77 -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.
37 +{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
78 78  
79 -== **Bug fixes ** ==
39 +//__3rd generation runtime debugger feedback__//
40 +We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality.
80 80  
81 -//__Keep selection when copying properties__//
82 -We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
42 +//__No "Shift key" needed anymore to select multiple items in the flow designer__//
43 +As of now you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows.
83 83  
84 -//__Check on security header improved for API Gateway__//
85 -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.
45 +//__User Management synchronization now happens in one step__//
46 +With this release we have updated the synchronization process between Design and Deploy with regards to User Management. From now on, when you press the "Transfer from design" button both Users and Roles will be synchronized.
86 86  
87 -//__Copy and paste default support objects__//
88 -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.
89 -
90 -//__Fix editability of properties when importing store items__//
91 -With this release, you can once again change property names upon importing a store item.
92 -
93 93  == **Fancy Forum Answers** ==
94 94  
95 95  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:
96 96  
97 -* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
98 -* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
99 -* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
100 100  * [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
53 +* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]]
54 +* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]]
101 101  
102 102  == **Key takeaways** ==
103 103