Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 117.1
edited by Erik Bakker
on 2023/05/22 14:03
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 -198 - Great Migration
1 +192 - Small Step
Content
... ... @@ -2,46 +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 few weeks, we have worked hard on improving the migration towards our next-generation architecture as well as improved the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our own infrastructure to ensure that all data flowing via this infrastructure now more and more customers are migrating can be handled as good if not better as before.
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 -== **3rd generation improvements and bug fixes** ==
7 +== **Start/Stop Flows** ~*~* ==
8 8  
9 -//__"Stop" action when running a hybrid situation is not causing issues anymore__//
10 -Before, it could happen when running a double-lane setup in a hybrid situation (i.e karaf based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release that behavior is changed.
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}}
11 11  
12 -{{info}}Note that this fix is part of a new runtime image for the karaf based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
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".
13 13  
14 -//__Removed certain dependencies between Deploy Architecture and Releases__//
15 -In this release, we have removed several specific dependencies that caused confusion between the functionality in the Deploy Architecture overview compared to the functionality that is linked to a release and specifically the deployment of a release.
13 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
16 16  
17 -//__Improved validation errors on invalid configuration of HTTP outbound components__//
18 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
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.
19 19  
20 -//__Improved migration behavior__//
21 -This release introduces several improvements with regards to the migration behavior via "Transfer settings from Design". Among these are a smoother migration of your JMS (and backup JMS) process, additional feedback given to the user and feedback when the migration process is finished.
17 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
22 22  
23 -//__Improved auto-healing when running in a hybrid situation__//
24 -In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
19 +{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
25 25  
26 -//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
27 -To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
21 +== **Manage overview Event Streaming** ~*~* ==
28 28  
29 -{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
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.
30 30  
25 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
26 +
31 31  == **Feedback items ** ==
32 32  
33 -//__Make sure the message format can be viewed without "Start editing"__//
34 -With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
29 +We have also solved other feedback items besides the flow designer's critical updates.
35 35  
36 -//__Various styling improvements in the flow testing functionality__//
37 -Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
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.
38 38  
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.
36 +
37 +{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
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.
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.
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.
47 +
39 39  == **Fancy Forum Answers** ==
40 40  
41 41  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:
42 42  
43 -* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
44 -* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
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"]]
45 45  
46 46  == **Key takeaways** ==
47 47