Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 46.1
edited by Erik Bakker
on 2022/11/21 12:31
Change comment: There is no comment for this version
To version 160.1
edited by Carlijn Kokkeler
on 2023/10/11 09:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +206 - Situational Deployment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -2,80 +2,81 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
6 6  
7 -== **3rd generation runtime bolstering** ==
7 +== **Deployment Plan** ==
8 8  
9 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it.
9 +//__Improved deployment plan to make the process better and more predictable__//
10 +The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
10 10  
11 -//__Migration of JMS backup configuration improved__//
12 +//__Editing release properties__//
13 +With this release, it will be possible to change the description of a property by editing the property.
12 12  
13 -//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 +//__JMS memory setting check__//
16 +A change in memory settings triggers redeployment of the container now.
14 14  
15 -//__Autogenerated exits can be deployed at once__//
18 +//__Properties tab__//
19 +We have removed the deprecated tab Properties in the Deploy phase.
16 16  
17 -//__Code mapping functionality available on 3rd generation runtime__//
21 +//__Cleanup old images__//
22 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
18 18  
19 -//__Improved the performance of deploying or activating a release__//
24 +//__Performance improvements for loading releases__//
25 +Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
20 20  
21 -//__Failing runtimes won't be restarted indefinetly anymore__//
27 +== **Store Improvements** ==
22 22  
23 -== **Exportable Release Audit** ~* ==
29 +//__Message definition elements order__//
30 +We fixed an issue that the orders of message definition’s elements were changed after imported.
24 24  
25 -On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
32 +== **Feedback Items** ==
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
34 +//__Alerting manual pause__//
35 +A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
28 28  
29 -{{warning}}Note that the following restrictions apply when exporting an audit document:
30 - * Changes made on definition and transformation level are **not** restored
31 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022
32 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
33 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
37 +//__Ordering of graphs in Manage__//
38 +The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
34 34  
35 -== **Feedback items ** ==
40 +//__UTC times in Grafana panels__//
41 +All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
36 36  
37 -We have also solved other feedback items besides the flow designer's critical updates.
43 +//__Update flow designer version__//
44 +The framework used in the flow designer has been updated to the latest version.
38 38  
39 -//__Data Sink Refactor__//
40 -We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end we will contact your seperately.
46 +//__Carwash track TLS versions in logging__//
47 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
41 41  
42 -//__Improved naming convention on Store related pages__//
43 -We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
49 +//__Moving channels in the flow designer__//
50 +Moving already attached channels in the flow designer has been made sligthly easier.
44 44  
45 -//__Press "Enter" to search on multiple pages__//
46 -In our Daemon Switch release we added functionality that allowed you to press **Enter** to search on the property overview page. With this release we have added this functionality to many more pages across the portal. The complete list is as follows
52 +//__Topic sizes description change__//
53 +In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
47 47  
48 -* Deploy → Deployment Plan
49 -* Deploy → Properties → History
50 -* Deploy → User Management → Roles
51 -* Manage → Error Messages → Error Messages
52 -* Manage → Error Messages → Flows with Error Messages
53 -* Manage → Error Messages → Exceptions of Error Messages
54 -* Manage → Log Entries
55 -* Manage → Alerts
56 -* Manage → Triggers
57 -* Manage → Tags – Cant find (only Gen2)
58 -* Manage → Notifications
59 -* Manage → Notification Settings
60 -* Manage → Data Usage → History
61 -* Manage → Code mappings → All tabs
55 +//__Password change notification__//
56 +When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
62 62  
58 +//__Password comparison__//
59 +When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
60 +
61 +
62 +== **Bug Fixes** ==
63 +
64 +//__Flow designer styling__//
65 +The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
66 +
63 63  == **Fancy Forum Answers** ==
64 64  
65 65  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:
66 66  
67 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
68 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
69 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
70 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
71 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
71 71  
72 72  == **Key takeaways** ==
73 73  
74 -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:
75 +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:
75 75  
76 76  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  * If you have feedback or ideas for us, talk to the Platypus
78 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
79 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
79 79  * Clear your browser cache (Ctrl + Shift + Del)
80 80  * Check out the release notes [here]
81 81  * Start thinking about how the license tracker can aid your development
... ... @@ -88,6 +88,6 @@
88 88  {{info}}
89 89  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
90 90  
91 -~*~* Indicates a GEN3-only feature.
92 +~*~* Indicates a next-generation-architecture only feature.
92 92  {{/info}})))((({{toc/}}))){{/container}}
93 93  {{/container}}