Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 155.1
edited by Carlijn Kokkeler
on 2023/10/10 13:56
on 2023/10/10 13:56
Change comment:
There is no comment for this version
To version 338.1
edited by Carlijn Kokkeler
on 2024/01/15 14:34
on 2024/01/15 14:34
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 06-SituationalDeployment1 +212 - Failover Fiesta - Content
-
... ... @@ -1,60 +1,29 @@ 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 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 +**Hi there, eMagiz developers!** This release... 6 6 7 -== **Deployment Plan** == 8 - 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 - 12 -//__Editing release properties__// 13 -With this release, it will be possible to change the description of a property by editing the property. 14 - 15 -//__JMS memory setting check__// 16 -A change in memory settings triggers redeployment of the container now. 17 - 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 - 26 26 == **Feedback Items** == 27 27 28 -//__ Alertingmanual pause__//29 - A fewreleases ago wechanged the behavior of alerting in the deploymentplan. Now each time whena deploymentplan isexecuted thealertingwillbeautomaticallyre-enabledwhenthe deployercloses the deploymentplanorclosestheweb browser. Themajority ofthe usersare happy withthenewbehavior,butthereare some use cases thatyoudonot wantstart thelertingmediately. With this release, ifalerting has been paused manually,this will not bectivated automatically aftera release deployment.10 +//__Failover setup__// 11 +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"]]. 30 30 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). 33 33 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. 36 - 37 -//__Update flow designer version__// 38 -The framework used in the flow designer has been updated to the latest version. 39 - 40 - 41 - 42 42 == **Bug Fixes** == 43 43 44 -//__ Gain thebility again to configurecertificates inDeploy Architecture again__//45 - Inrestricting theconfigurationoptionsonthecertificatelevel inneof ourlatterreleases,itbecameimpossiblefornormaluserstoaddandedit certificateswithin DeployArchitecture.Toresolve this problemwehavenowreleasedafixtoresolve thisissue,giving peoplebility again to addandeditcertificates underDeployArchitecture.16 +//__Message merging tool__// 17 +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. 46 46 47 -//__ Ensure thatdiffering container configurations deploy thecorrectconfiguration__//48 - Whenyourun in a multi-runtimeconfigurationandchangetheactualflowsthatneedtorunon containerA vs.container B, ithappenedbefore that all flowswerestill beingdeployed on all runtimes.With thisrelease,wewill feed this informationcorrectlytoourinfrastructureto ensurehecorrectandconfiguredflows aredeployedon thepropercontainers.19 +//__Catalog topic definitions__// 20 +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. 49 49 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. 52 - 53 53 == **Fancy Forum Answers** == 54 54 55 55 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: 56 56 57 -* [[ Gettingfiles fromsubfolders(FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]26 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]] 58 58 59 59 == **Key takeaways** == 60 60 ... ... @@ -67,7 +67,6 @@ 67 67 * Check out the release notes [here] 68 68 * Start thinking about how the license tracker can aid your development 69 69 * Start thinking about major, minor, and patch 70 -* Upgrade to the latest build number 71 71 * Keep making great integrations 72 72 73 73 Let's stay in touch and till next time! ... ... @@ -75,6 +75,11 @@ 75 75 {{info}} 76 76 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 77 77 78 -~*~* Indicates a next-generation-architecture only feature. 79 -{{/info}})))((({{toc/}}))){{/container}} 46 +{{/info}} 47 +))) 48 + 49 +((( 50 +{{toc/}} 51 +))) 80 80 {{/container}} 53 +{{/container}}