Changes for page 206 - Situational Deployment
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
From version 91.1
edited by Erik Bakker
on 2023/03/14 06:52
on 2023/03/14 06:52
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 194-BigLeap1 +206 - Situational Deployment - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -2,74 +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 coupleofweeks, we haveworkedaround the clocktoeleasevarious improvementspoints within the3rd generationruntimeand elsewhere.Amongotherswe haveimproved the feedback providedwhen a flow can'tstart dueto an incorrect transformation. Improvedwhenertain logging is triggerdand improved the stability of ourinternal infrastructure.Ontopofthatwefixedseveralbugfixessurroundingotherpartsoftheplatform. So withoutfurtherado letus takea lookat all theseimprovements.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 improvements** ==7 +== **Deployment Plan** == 8 8 9 -//__ Betterfeedbackinerrorlog when acorruptstylesheetis encountered__//10 - Wehaveimproved thelogging withina 3rdgenerationruntimethatidentifiesthe brokenresourceby namewithinacontainer andinforms you tonavigate toCreate-> Resourcestoseeinhichflowstheresource isusedsoucantakethe appropriate action.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 -//__ Betterinternal error handlingto avoid unnecessaryalerting and notifications__//13 -W e haveimprovedtheinternal errorhandlingwhensendingmetricsfrom theruntime toour monitoring stack. This will gravelyreducethenumber of alertsyouwill receive onthistopic whenyourmodelruns onthe 3rd generation monitoring stack.12 +//__Editing release properties__// 13 +With this release, it will be possible to change the description of a property by editing the property. 14 14 15 -//__ ImprovedManageDashboard__//16 - Thisrelease improves what youcanseeinthe Manage Dashboardafteryou migrated yourmodel3rd generationruntimearchitecture.15 +//__JMS memory setting check__// 16 +A change in memory settings triggers redeployment of the container now. 17 17 18 -//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__// 19 -When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes. 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 + 20 20 21 -//__Improved process of deploy preparation__// 22 -With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced. 26 +== **Feedback Items** == 23 23 24 -//__ Improved migrationof Streamingcontainer__//25 - Whenmigratingyourstreamingcontainerwe nowtakeinto account whether"customerrorhandling"isused within one ofthe event processors. Basedonthatdeterminationspecificadditionalcomponentsare addedto ensure that thestreamingcontainer willworkaftermigratingwithoutanymanual intervention.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. 26 26 27 -//__ Add HistorytoNotifications in Manage__//28 -T o improve the auditabilityof our platform wehaveintroduced an audittrailtotheNotificationsectionin Manageformodelsrunningon our 3rdgenerationmonitoringstack. Thiswayitisalwaysvisiblewhenthenotificationswerepausedandwho pausedornpausedthenotifications.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). 29 29 30 -//__ ImprovedManagephasefor EventStreaming__//31 - Basedon thefeedbackon ourfirst iterationoftheManage phaseforEventStreamingwehaveimprovedthegraphs andthecalculationsthat fillthegraphs withvalues. Ontop of that wehaveadded helptextstoclarifywhateach graph ourtable displays to you.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. 32 32 33 -//__ Improvedhelptextfornetworkvolumes__//34 - Withthisreleaseehave improvedthehelptextthat explainsnetwork volumesandhowtousethemwithinourolution.37 +//__Update flow designer version__// 38 +The framework used in the flow designer has been updated to the latest version. 35 35 36 -{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}} 37 37 38 -== **Feedback items ** == 41 + 42 +== **Bug Fixes** == 39 39 40 -//__ RemovedODataasoptionfor anAPI Gatewayoperation__//41 - Withthisrelease,wehave removedtheODataoperation optionas itwas notused andwasnotfullysupportedanymorebythe platform.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. 42 42 43 -//__ Changes inAPI Gatewayoperation pathsis automatically updatedinCreate__//44 -When you changeyourpathon a hosted APIGatewaywewill nowautomaticallyupdate theaccompanyingcomponent inyourCreate(all-)entry.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. 45 45 46 -{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}} 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. 47 47 48 -== **Bug fixes ** == 49 - 50 -//__Prevent endless loop in Deploy -> User Management__// 51 -With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion. 52 - 53 -{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}} 54 - 55 -//__Update error handling during migration to the 3rd generation runtime__// 56 -As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration. 57 - 58 58 == **Fancy Forum Answers** == 59 59 60 60 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: 61 61 62 -* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]] 63 -* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]] 64 -* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]] 57 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 65 65 66 66 == **Key takeaways** == 67 67 68 -Thanks to all thathelped 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: 69 69 70 70 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 71 71 * If you have feedback or ideas for us, talk to the Platypus 72 -* 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. 73 73 * Clear your browser cache (Ctrl + Shift + Del) 74 74 * Check out the release notes [here] 75 75 * Start thinking about how the license tracker can aid your development ... ... @@ -82,6 +82,6 @@ 82 82 {{info}} 83 83 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 84 84 85 -~*~* Indicates a GEN3-only feature.78 +~*~* Indicates a next-generation-architecture only feature. 86 86 {{/info}})))((({{toc/}}))){{/container}} 87 87 {{/container}}