Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 182.1
edited by Carlijn Kokkeler
on 2023/10/12 16:18
on 2023/10/12 16:18
Change comment:
There is no comment for this version
To version 335.1
edited by Carlijn Kokkeler
on 2024/01/15 14:14
on 2024/01/15 14:14
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,114 +1,44 @@ 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 -== **Release Date Change** == 8 -As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM CET (4:00 UTC). We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 9 - 10 -== **Deployment Plan** == 11 - 12 -//__Improved deployment plan to make the process better and more predictable__// 13 -The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is stopped last, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally, and all processes are stopped before being deployed again. This provides additional control over the deployment of your release(s) and reduces the likelihood of false-positive logging (and potentially alerting) during and shortly after the deployment. 14 - 15 -{{info}}The start/stop/restart machine deployment steps work for cloud and on-premises machines.{{/info}} 16 - 17 -//__Editing release properties__// 18 -With this release, it will be possible to change the description of a property by editing the property. 19 - 20 -//__Container memory settings__// 21 -A change in memory settings triggers redeployment of the container now. 22 - 23 -//__Properties tab__// 24 -We have removed the deprecated tab Properties in the Deploy phase. 25 - 26 -//__Cleanup old images__// 27 -When a release is removed, the related unused images in the on-premises machines will be removed as well. 28 - 29 -//__Performance improvements for loading releases__// 30 -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. 31 - 32 -== **Store Improvements** == 33 - 34 -//__Message definition elements order__// 35 -We fixed an issue that the order of message definition elements was changed after being imported. 36 - 37 -//__Importing a store item with synchronous message definitions__// 38 -We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions. 39 - 40 -//__Importing store items containing static copies__// 41 -We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly. 42 - 43 -//__Importing store content__// 44 -We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store. 45 - 46 -//__Store disclaimer__// 47 -Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer. 48 - 49 49 == **Feedback Items** == 50 50 51 -//__ Alertingmanual pause__//52 - 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"]] 53 53 54 -//__Ordering of graphs in Manage__// 55 -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). 13 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]] 56 56 57 -//__ UTCtimes in Grafana panels__//58 - AllGrafana panelsnowshowUTCtimes,whichare normally usedineMagiz, instead oflocal(browser)timezones. Thisway, it iseasierto matchgraphswithloggingeventsor alerts.15 +//__External recipients emailaddress__// 16 +The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users. 59 59 60 -//__ Updateflow designerversion__//61 - Theframework usedinthe flowdesignerhasbeenupdatedto thelatestversion.18 +//__Broker queue metrics dashboards__// 19 +It is now possible to select the MQTT broker in the queue metrics dashboards. 62 62 63 -//__ CarwashtrackTLSversions in logging__//64 - A newloggingfeaturewillbe released,enabling usto make betterchoicesindeprecatingold encryptionstandards.21 +//__Runtime image version__// 22 +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. 65 65 66 -//__Moving channels in the flow designer__// 67 -Moving already attached channels in the flow designer has been made sligthly easier. 68 68 69 -//__Topic sizes description change__// 70 -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. 71 - 72 -//__Password change notification__// 73 -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. 74 - 75 -//__Password comparison__// 76 -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. 77 - 78 -//__Inactive user alerting__// 79 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications. 80 - 81 -//__Alphabetical sorting on user level in HTTP statistics__// 82 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. 83 - 84 -//__SOAP Web services path__// 85 -Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings. 86 - 87 87 == **Bug Fixes** == 88 88 89 -//__ Flow designerstyling__//90 -The s tyling oftheflowdesigner'sleft componentpanel hasbeen restructured,solvinga rarebug which wouldbreakthestylingofcertainfunctionalities.27 +//__Message throughput__// 28 +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. 91 91 92 -//__ Partialsearchformessages__//93 - Itisnow possibleto searchonmessagespartiallyin ManageMonitoring.Forexample,asearchforUptime canbedone by searching for"up""time""ptim".30 +//__Cloud template upgrade incorrect rollback__// 31 +An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks. 94 94 95 -//__ Diskusageaftercloud templateupdate__//96 - In the last cloud templateupdatetherewas an issuewithdisk performance.This has been resolvedin thisrelease. You can manuallyupgradeyourcloudtemplate,orrelyonautomatic updates.33 +//__Next generation block__// 34 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 97 97 98 -//__Error handling migration__// 99 -If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false. 100 - 101 101 == **Fancy Forum Answers** == 102 102 103 103 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: 104 104 105 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] 106 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]] 107 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]] 108 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]] 109 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]] 40 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]] 110 110 111 - 112 112 == **Key takeaways** == 113 113 114 114 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: ... ... @@ -120,7 +120,6 @@ 120 120 * Check out the release notes [here] 121 121 * Start thinking about how the license tracker can aid your development 122 122 * Start thinking about major, minor, and patch 123 -* Upgrade to the latest build number 124 124 * Keep making great integrations 125 125 126 126 Let's stay in touch and till next time! ... ... @@ -128,6 +128,11 @@ 128 128 {{info}} 129 129 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 130 130 131 -~*~* Indicates a next-generation-architecture only feature. 132 -{{/info}})))((({{toc/}}))){{/container}} 60 +{{/info}} 61 +))) 62 + 63 +((( 64 +{{toc/}} 65 +))) 133 133 {{/container}} 67 +{{/container}}