Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 339.1
edited by Carlijn Kokkeler
on 2024/01/15 14:39
Change comment: There is no comment for this version
To version 156.1
edited by Carlijn Kokkeler
on 2023/10/10 13:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +206 - Situational Deployment
Content
... ... @@ -1,37 +1,52 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release...
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.
7 7  
8 -== **Cloud Template R20 - Double Lane** ==
7 +== **Deployment Plan** ==
9 9  
10 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R20 - Double lane.WebHome||target="blank"]].
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.
11 11  
12 -== **Cloud Template R27 - Single Lane** ==
12 +//__Editing release properties__//
13 +With this release, it will be possible to change the description of a property by editing the property.
13 13  
14 -This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
15 +//__JMS memory setting check__//
16 +A change in memory settings triggers redeployment of the container now.
15 15  
18 +//__Properties tab__//
19 +We have removed the deprecated tab Properties in the Deploy phase.
20 +
21 +//__Cleanup old images__//
22 +
23 +== **Store Improvements** ==
24 +
25 +
16 16  == **Feedback Items** ==
17 17  
18 -//__Failover setup__//
19 -New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
28 +//__Alerting manual pause__//
29 +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.
20 20  
31 +//__Ordering of graphs in Manage__//
32 +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).
21 21  
22 -== **Bug Fixes** ==
34 +//__UTC times in Grafana panels__//
35 +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.
23 23  
24 -//__Message merging tool__//
25 -The message merging tool has been fixed to allow merging a store item message model into your own message models. In some rare cases your CDM message may be broken due to incorrect data. In those cases, the message mapping and message merge functionalities will be broken as well. If this broken data is detected when navigating to CDM-message-related pages, you will be able to clean your CDM message.
37 +//__Update flow designer version__//
38 +The framework used in the flow designer has been updated to the latest version.
26 26  
27 -//__Catalog topic definitions__//
28 -It is now possible to generate a JSON Example of a topic whose schema has nested elements. Before, an error would occur when trying to generate a JSON example in this case.
29 29  
41 +
42 +== **Bug Fixes** ==
43 +
44 +
30 30  == **Fancy Forum Answers** ==
31 31  
32 32  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:
33 33  
34 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
49 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
35 35  
36 36  == **Key takeaways** ==
37 37  
... ... @@ -44,6 +44,7 @@
44 44  * Check out the release notes [here]
45 45  * Start thinking about how the license tracker can aid your development
46 46  * Start thinking about major, minor, and patch
62 +* Upgrade to the latest build number
47 47  * Keep making great integrations
48 48  
49 49  Let's stay in touch and till next time!
... ... @@ -51,11 +51,6 @@
51 51  {{info}}
52 52  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
53 53  
54 -{{/info}}
55 -)))
56 -
57 -(((
58 -{{toc/}}
59 -)))
70 +~*~* Indicates a next-generation-architecture only feature.
71 +{{/info}})))((({{toc/}}))){{/container}}
60 60  {{/container}}
61 -{{/container}}