Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 121.1
edited by Erik Bakker
on 2023/06/05 15:02
on 2023/06/05 15:02
Change comment:
There is no comment for this version
To version 56.1
edited by Erik Bakker
on 2022/12/06 14:58
on 2022/12/06 14:58
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 -19 9-Home Improvements1 +189 - Private Eye - Content
-
... ... @@ -2,45 +2,71 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Inthetfewweeks,we haveworkedhard onmprovingvarious aspectsofourhome.Amongotherswehaveimprovedthelogging,alerting,andsecurityofour next-generationarchitecture. On top of that wehave improved the inner workings ofthestore andthecertificatemanagementforfususingtheEventStreamingpattern.5 +**Hi there, eMagiz developers!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community. 6 6 7 -== **Next generation improvements and bug fixes** == 7 +== **Private Store** == 8 +On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved). 8 8 9 -//__Enhanced overview of the HTTP Statistics__// 10 -As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort. 10 +{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}} 11 11 12 -//__Reason why runtime cannot start is now in the vast majority of cases reported back__// 13 -In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup. 12 +== **3rd generation runtime bolstering** == 14 14 15 - {{info}}Notethat thisfixis partf a newruntimeimage forthenext-generation runtimes.Thereleasenotesofthiscanbefound[[here>>doc:Main.ReleaseInformation.RuntimeImages.WebHome||target="blank"]]{{/info}}14 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal. 16 16 17 -//__ Forced congestion control__//18 - Toreducethenumberofrepeatingmailswithina10minutewindowwehavenowforcedcongestioncontrolon all alertsgeneratedvia the platform.16 +//__SOAP and REST web services migration including splitting them__// 17 +With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime and at the same time you can directly split the all-entry to get rid of that construction alltogether. A specific migration path for this will be published in the documentation portal. 19 19 20 -//__ Unusedimagesarecleanedup__//21 - Thisreleaseimprovestheway in which imagesarekept.To avoid a lot of old andunusedimageson oursystems and oursystemswenow(on default)cleanup old imagesthat arenot used anymore.Shouldyou wish to keeptheimagesandmanually removethemon yourownserveryoucandeactivatethis behaviorper"Deploy machine" stepinyourdeploymentplan.19 +//__Changing SSL settings for 3rd generation runtime models works__// 20 +As with the current runtime architecture, you can now also change the SSL settings if needed for a model running in the 3rd generation runtime. 22 22 23 -//__Improved rollup and storage ofmetrics when runningan event streamingsolution__//24 -T oimprove thestabilityoftheManagephase and, in particular, the metrics whenzoomingoutntheprovidedinformation,we have made some structural changesthat support this user functionality better.22 +//__Improved migration for JMS flows__// 23 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime. 25 25 26 -{{warning}} Dueto this change, the platformwillremove data collectedbeforetherelease date in the upcomingweeks.This processwill be finishedat thebeginning of July. Fromthenon,alldata beforehe9thof Junewill nolongerbevisible. As users generallydonotlook backthisfar back in time,weconsider thisanacceptable trade-off.{{/warning}}25 +{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}} 27 27 28 -== **Store Improvements** == 27 +//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__// 28 +As of this release, you cannot add debug components anymore on a flow that is already migrated to the 3rd generation runtime. This is because this functionality will not work in the 3rd generation runtime and would break your flow. 29 29 30 -//__ Improvedimportingbehaviorforspecificusecases__//31 - Before,it couldhappenthata certainplaceholderthatcontained anasterisk were imported incorrectly.This hasnowbeenfixed toensurethat thecorrectimport behavior isexperiencedby oursers.30 +//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__// 31 +We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime. 32 32 33 -== ** Event Streaming- CertificateManagement** ==33 +== **Feedback items ** == 34 34 35 -//__Expired certification notification__// 36 -As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 35 +We have also solved other feedback items besides the flow designer's critical updates. 37 37 37 +//__Improved naming convention on Store related pages__// 38 +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. 39 + 40 +//__Press "Enter" to search on multiple pages__// 41 +In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows. 42 + 43 +* Deploy → Deployment Plan 44 +* Deploy → Properties → History 45 +* Deploy → User Management → Roles 46 +* Manage → Error Messages → Error Messages 47 +* Manage → Error Messages → Flows with Error Messages 48 +* Manage → Error Messages → Exceptions of Error Messages 49 +* Manage → Log Entries 50 +* Manage → Alerts 51 +* Manage → Triggers 52 +* Manage → Tags – Cant find (only Gen2) 53 +* Manage → Notifications 54 +* Manage → Notification Settings 55 +* Manage → Data Usage → History 56 +* Manage → Code mappings → All tabs 57 + 58 +== **Bug fixes ** == 59 + 60 +//__Loading problems of Deployment plan execution overview__// 61 +We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases. 62 + 38 38 == **Fancy Forum Answers** == 39 39 40 40 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: 41 41 42 -* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]] 43 -* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]] 67 +* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]] 68 +* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]] 69 +* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]] 44 44 45 45 == **Key takeaways** == 46 46