Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 138.1
edited by Erik Bakker
on 2023/08/01 14:28
Change comment: There is no comment for this version
To version 151.1
edited by Erik Bakker
on 2023/09/13 07:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -202 - New Equilibrium
1 +205 - World Explorers
Content
... ... @@ -2,73 +2,67 @@
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 crossed our t's and dotted our i's on the release properties functionality that will impact the day-to-day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that, we have several smaller feedback items from our hackathon efforts that are now released to you.
5 +**Hi there, eMagiz developers!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
6 6  
7 -== **Release Properties** ==
8 -As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are:
7 +== ** Mandatory Cloud Template Upgrade - Next-generation models ** ==
9 9  
10 -* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
11 -* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration.
12 -* When adding or editing a property, you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers.
13 -* A, for most, a new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment.
9 +As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
14 14  
15 -{{info}}For more information, please check out the following microlearnings:
11 +== **Feedback Items** ==
16 16  
17 -* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
18 -* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
19 -* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
13 +//__Improved Validation when migrating to the next-generation architecture__//
14 +To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
20 20  
21 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
22 -{{/info}}
16 +{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
23 23  
24 -== ** Manage - Next generation graphs improvements ** ==
25 -As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out.
18 +//__Improved HTTP Statistics__//
19 +To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
21 +//__"Topic Full" alert restriction changed__//
22 +With this release, we will change the "Topic Full" trigger point in our standard set of alerts once a model uses the Event Streaming functionality. Before, the alert would trigger on 80%, but as we saw, this is too early to make the alert useful in the context of our customers. As a result, the threshold has been raised to 95% to accommodate real-life situations better.
28 28  
29 -== **Feedback Items** ==
24 +//__Improved performance Manage Dashboards__//
25 +We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
30 30  
31 -//__Improved editability when testing in eMagiz without Edit rights in Create__//
32 -Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description.
27 +//__Show values on the runtime level in Deploy Architecture__//
28 +We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
33 33  
34 -//__Improved auditability on Deploy Architecture__//
35 -To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP).
30 +{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
31 +* JMS - The number of queues in the active release.
32 +* Messaging Container - The number of messaging integrations in the active release.
33 +* Messaging Connector - The number of messaging integrations related to this system in the active release.
34 +* API Gateway Container - The number of operations in the active release.
35 +* Event Streaming Container - The number of event processors in the active release.
36 36  
37 -//__Test your own exported store content__//
38 -We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store.
37 +There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
39 39  
40 -{{info}}In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-magic-store.WebHome||target="blank"]]{{/info}}
41 -
42 -//__Improved comparison of flows in the releases overview__//
43 -We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.
44 -
45 45  == **Bug Fixes** ==
46 46  
47 -//__Improved validation on XPath header enricher__//
48 -To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.
41 +//__Improved information Queue Statistics__//
42 +Given several constraints, it could happen that specific queues needed to be correctly displayed within the Manage phase on your model, making it tough to manage them. This has been resolved with this release.
49 49  
50 -//__Cancel behavior on flow testing property overview fixed__//
51 -We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list.
44 +//__Gain the ability again to configure certificates in Deploy Architecture again__//
45 +In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
52 52  
53 -//__Cancel behavior on flow fragment level when exporting store content__//
54 -We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.
47 +//__Ensure that differing container configurations deploy the correct configuration__//
48 +When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
55 55  
56 -//__Adding numbers on containers in Deploy Architecture__//
57 -With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release.
50 +//__Remove queurying options in Manage__//
51 +To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
58 58  
59 59  == **Fancy Forum Answers** ==
60 60  
61 61  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:
62 62  
63 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
57 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
64 64  
65 65  == **Key takeaways** ==
66 66  
67 -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:
61 +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:
68 68  
69 69  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70 70  * If you have feedback or ideas for us, talk to the Platypus
71 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
65 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
72 72  * Clear your browser cache (Ctrl + Shift + Del)
73 73  * Check out the release notes [here]
74 74  * Start thinking about how the license tracker can aid your development
... ... @@ -81,6 +81,6 @@
81 81  {{info}}
82 82  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
83 83  
84 -~*~* Indicates a GEN3-only feature.
78 +~*~* Indicates a next-generation-architecture only feature.
85 85  {{/info}})))((({{toc/}}))){{/container}}
86 86  {{/container}}