Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 83.1
edited by Erik Bakker
on 2023/02/14 15:33
Change comment: There is no comment for this version
To version 312.1
edited by Carlijn Kokkeler
on 2023/12/21 14:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -192 - Small Step
1 +211 - Log Luminary
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,65 +1,78 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
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 essential things that will be released later this Q. On top of that, we finished additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the other features, we have a new event streaming graph and general updates to our platform.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **Start/Stop Flows** ~*~* ==
8 +== **TBD** ==
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}}
10 10  
11 -To enhance your options 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 the runtime level, you can open the context menu and select the "Start/Stop Flows" option.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
12 +== **Feedback Items** ==
14 14  
15 -After selecting the option, eMagiz will open a pop-up where you can stop and start the starting point of each flow deployed on that runtime. This effect is that the flow will process no new messages, but the flow will still process all remaining messages after stopping the flow. To prevent a flow, you select a flow and press the Stop button. To start it again, press Start.
14 +//__Runtime overview__//
15 +We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
17 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
18 18  
19 -{{info}}Only in "Start Editing" mode can you start and stop specific flows{{/info}}
19 +//__Missing properties overview__//
20 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
20 20  
21 -== **Manage overview Event Streaming** ~*~* ==
22 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-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 streaming statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, you can see metadata information on all your topics by clicking on the "Event streaming statistics" overview. Among others, you can see whether data is consumed, on which topic much data is produced, and whether consumers are lagging in consuming data.
24 +//__Breaking changes pop-up__//
25 +Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
27 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
26 26  
27 -== **Feedback items ** ==
29 +//__External recipients emailaddress__//
30 +The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
28 28  
29 -We have also solved other feedback items besides the flow designer's critical updates.
32 +//__Broker queue metrics dashboards__//
33 +It is now possible to select the MQTT broker in the queue metrics dashboards.
30 30  
31 -//__Topic configuration calculation__//
32 -With this release, we have simplified the configuration of settings on the topic level to enforce certain best practices within the portal and simultaneously make it easier to configure topics.
35 +//__Runtime image version__//
36 +The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
33 33  
34 -//__Make preparation step in deployment plan visible__//
35 -For deployment on the 3rd generation runtime to work, the portal needs some preparation work. We have now made this step explicit and part of the deployment plan.
38 +== **Bug Fixes** ==
36 36  
37 -{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
40 +//__Message throughput__//
41 +The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
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.
43 +//__Deployment execution error message__//
44 +In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup.
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.
46 +//__Cloud template upgrade unjust rollback__//
47 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3.
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 concerning User Management. When you press the "Transfer from design" button, both Users and Roles will be synchronized.
49 +//__Missing log entries__//
50 +We improved crash handling so that log messages clearly show when and why a container failed to start.
47 47  
52 +//__Runtime logging__//
53 +We fixed a bug where no new log messages were showing up, even though they were produced by the container.
54 +
55 +
56 +
57 +
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  
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"]]
62 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
63 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
64 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
65 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
66 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
55 55  
68 +
56 56  == **Key takeaways** ==
57 57  
58 -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:
71 +Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
59 59  
60 60  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61 61  * If you have feedback or ideas for us, talk to the Platypus
62 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
75 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
63 63  * Clear your browser cache (Ctrl + Shift + Del)
64 64  * Check out the release notes [here]
65 65  * Start thinking about how the license tracker can aid your development
... ... @@ -72,6 +72,12 @@
72 72  {{info}}
73 73  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74 74  
75 -~*~* Indicates a GEN3-only feature.
76 -{{/info}})))((({{toc/}}))){{/container}}
88 +~*~* Indicates a next-generation-architecture only feature.
89 +{{/info}}
90 +)))
91 +
92 +(((
93 +{{toc/}}
94 +)))
77 77  {{/container}}
96 +{{/container}}