Skip to Content

Changes for page 194 - Giant Leap

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -192 - Small Step
1 +191 - Fifty Fifty
Content
... ... @@ -2,56 +2,123 @@
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 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.
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.
6 6  
7 -== **Start/Stop Flows** ~*~* ==
7 +== **Dynamic Alerts** ~*~* ==
8 8  
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}}
9 +{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
10 10  
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".
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 the "Queue browser." You can access this functionality via the "Explore" menu in Manage. Then, with the help of the queue browser, you can browse your queue as the name suggests.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
13 +To do so, we offer two options within this functionality. First, we have the Explore function, and we have the Wiretap function. When selecting a queue and opting for the Explore option, you get a live view of the current data in the queue. Then, when choosing the Wiretap functionality, you automatically wiretap your queue and are presented with copies (on a particular queue) of your actual message that passes through the queue from the moment you press the Wiretap button.
14 14  
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.
15 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
17 +After selecting the queue and choosing the option, eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option), or that passed the queue since the moment you activate the option (Wiretap option). For each message, you have various options at your disposal.
18 18  
19 -{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
19 +* Delete the message from the queue (Explore option)
20 + ** This means throwing away live data, which can be helpful in a test or acceptance environment where you inadvertently put many messages on a queue.
21 +* Clear message from the wiretap queue (Wiretap option)
22 + ** Once you are done with the analysis of a specific message in the wiretap functionality, you can clear it from the overview so it does not clutter the view anymore
23 +* Refresh messages list (both options)
24 + ** By pressing this button, you can refresh the list of messages displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
25 +* Save as test message
26 + ** By pressing this button, you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so, we link the message to your model so you can still use it in the flow testing functionality.
27 +* Download
28 + ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
20 20  
21 -== **Manage overview Event Streaming** ~*~* ==
30 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
22 22  
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.
32 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
34 +{{info}}The following restrictions apply to this functionality:
35 + * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
36 + * The wiretap functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
37 + ** After five minutes the wiretap functionality will be shutdown automatically under water.
38 + ** To see new messages after the five minutes you will have to access the wiretap functionality again from scratch.{{/info}}
26 26  
40 +== **Debugger ** ~*~* ~* ==
41 +
42 +{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime, and the functionality is enabled for your environment.{{/warning}}
43 +
44 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
45 +
46 +As with our current offering, we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience, we have placed this functionality under the "Explore" option in Manage. When selecting the message redelivery option, you will see all messages that currently need to be redelivered (as an error occurred).
47 +
48 +As in the current functionality, you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that, you can still see the linked error message as you could before.
49 +
50 +On top of that, we have added some additional functionality.
51 +
52 +* Search option
53 + ** Original queue name
54 + ** Original message ID (which can be found as a header called jms_messageid in the error message view)
55 +* Save as test message
56 + ** By pressing this button, you can save the message and use it in our flow testing functionality in Create.
57 +* Download
58 + ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
59 +
60 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
61 +
62 +== **3rd generation runtime bolstering** ==
63 +
64 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
65 +
66 +//__Define memory settings for on-premise runtimes from Deploy Architecture__//
67 +With this release, you can now define the memory settings (and, therefore, the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases, you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes, you need to create a new release and deploy it to actualize the changes on-premise.
68 +
69 +//__Empty runtime feedback when deploying a release (or setting the release as active)__//
70 +To prevent you are not being able to deploy a release to your environment due to a mismatch between what is in your release and Deploy Architecture, we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.
71 +
72 +//__Auto-fill namespaces for SOAP hosted webservices__//
73 +Based on your configuration in Design, eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages.
74 +
75 +//__Updated H2 database setting__//
76 +As of this release, we have improved the configuration of our H2 databases used within eMagiz. This new setting will ensure the runtime controls when the H2 database is shut down.
77 +
78 +{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}}
79 +
80 +//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
81 +As a replacement for the current HTTP settings context menu, we added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service), you now also can define whether the control bus needs to work for this runtime.
82 +
83 +//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
84 +With this release, we have added a context menu item allowing users to deploy the agent needed to run your 3rd generation architecture on-premise. For more information on installing this, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
85 +
86 +//__Performance improvement creating a release__//
87 +With this release, we have improved the performance of creating a release.
88 +
27 27  == **Feedback items ** ==
28 28  
29 29  We have also solved other feedback items besides the flow designer's critical updates.
30 30  
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.
93 +//__Sensitive information stored in properties is masked __//
94 +We have made how we display sensitive information across the portal similar for various parts of the portal.
33 33  
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.
96 +//__Importing "Private" store content to which you do not have access__//
97 +We have improved the user feedback a user will get when trying to import a "Private" store item unavailable to the user.
36 36  
37 -{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
38 38  
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.
100 +== **Bug fixes ** ==
41 41  
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.
102 +//__Fix the possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
103 +We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
44 44  
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.
105 +//__Synchronization of Event Streaming topic states__//
106 +We fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
47 47  
108 +//__Copy and paste default support objects__//
109 +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.
110 +
111 +//__Fix editability of properties when importing store items__//
112 +With this release, you can once again change property names upon importing a store item.
113 +
48 48  == **Fancy Forum Answers** ==
49 49  
50 50  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:
51 51  
118 +* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
119 +* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
120 +* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
52 52  * [[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"]]
55 55  
56 56  == **Key takeaways** ==
57 57