Changes for page 206 - Situational Deployment
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
From version 83.1
edited by Erik Bakker
on 2023/02/14 15:33
on 2023/02/14 15:33
Change comment:
There is no comment for this version
To version 151.1
edited by Erik Bakker
on 2023/09/13 07:02
on 2023/09/13 07:02
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 - 192 -SmallStep1 +205 - World Explorers - Content
-
... ... @@ -2,64 +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 thelastcouple ofweeks,weworkedhard onbuildingseveralessentialthingsthatwillbe released laterthisQ. On top of that, wefinishedadditional featuresforour3rdgenerationruntimethatgiveyouhirurgicalprecision whendoingmaintenanceona model.Among theother features,wehavea neweventstreaming graphand general updatesto ourplatform.5 +**Hi there, eMagiz developers!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider. 6 6 7 -== ** Start/StopFlows**~*~* ==7 +== ** Mandatory Cloud Template Upgrade - Next-generation models ** == 8 8 9 - {{warning}}Notethat dependingonthe alert,thisfunctionalitywillonly workwhenyourJMSserverisrunningonthe3rdgenerationruntime{{/warning}}9 +As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains. 10 10 11 - Toenhanceyour options when running into problems or when maintaining your solution in a Productionenvironment, wehave added a new feature to our Deploy phase called "Start/Stop Flows." You can access this functionality via the "Deploy Architecture" overview in Deploy. On the runtime level, you can open the context menu andselectthe "Start/Stop Flows" option.11 +== **Feedback Items** == 12 12 13 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]] 13 +//__Improved Validation when migrating to the next-generation architecture__// 14 +To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture. 14 14 15 - After selecting theoption,eMagizwill open a pop-up where you can stopand start thestartingpointofeach flow deployed on that runtime.Thiseffect is that the flow will processno new messages,buttheflow will stillprocess allremainingmessagesafter stopping the flow. To prevent a flow,youselectflow and presstheStop button. To starttagain, press Start.16 +{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}} 16 16 17 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]] 18 +//__Improved HTTP Statistics__// 19 +To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview. 18 18 19 -{{info}}Only in "Start Editing" mode can you start and stop specific flows{{/info}} 21 +//__"Topic Full" alert restriction changed__// 22 +With this release, we will change the "Topic Full" trigger point in our standard set of alerts once a model uses the Event Streaming functionality. Before, the alert would trigger on 80%, but as we saw, this is too early to make the alert useful in the context of our customers. As a result, the threshold has been raised to 95% to accommodate real-life situations better. 20 20 21 -== **Manage overview Event Streaming** ~*~* == 24 +//__Improved performance Manage Dashboards__// 25 +We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture. 22 22 23 -To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaming statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, you can see metadata information on all your topics by clicking on the "Event streaming statistics" overview. Among others, you can see whether data is consumed, on which topic much data is produced, and whether consumers are lagging in consuming data. 27 +//__Show values on the runtime level in Deploy Architecture__// 28 +We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]] 30 +{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence. 31 +* JMS - The number of queues in the active release. 32 +* Messaging Container - The number of messaging integrations in the active release. 33 +* Messaging Connector - The number of messaging integrations related to this system in the active release. 34 +* API Gateway Container - The number of operations in the active release. 35 +* Event Streaming Container - The number of event processors in the active release. 26 26 27 - ==**Feedbackitems**==37 +There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}} 28 28 29 - Wehave also solved other feedback items besides the flow designer'scritical updates.39 +== **Bug Fixes** == 30 30 31 -//__ Topic configurationcalculation__//32 - Withthisrelease, we havesimplifiedtheconfigurationof settings onthe topiclevelto enforceertainbestpracticeswithin the portal andsimultaneouslymakeitiertoconfiguretopics.41 +//__Improved information Queue Statistics__// 42 +Given several constraints, it could happen that specific queues needed to be correctly displayed within the Manage phase on your model, making it tough to manage them. This has been resolved with this release. 33 33 34 -//__ Makepreparationstepindeploymentplan visible__//35 - Fordeployment on the3rd generationruntimetowork, the portalneedssomepreparationwork.We have nowmade this stepexplicit andpartofhe deploymentplan.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. 36 36 37 -{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}} 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. 38 38 39 -//__ 3rd generationruntimedebugger feedback__//40 - Wehave improvedthe userexperienceofthe3rdgenerationruntime debugger withthisreleasebysolvingvariousfeedbackitemswenoticedinthefirstdoptionsof thefunctionality.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. 41 41 42 -//__No "Shift key" needed anymore to select multiple items in the flow designer__// 43 -As of now, you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows. 44 - 45 -//__User Management synchronization now happens in one step__// 46 -With this release, we have updated the synchronization process between Design and Deploy concerning User Management. When you press the "Transfer from design" button, both Users and Roles will be synchronized. 47 - 48 48 == **Fancy Forum Answers** == 49 49 50 50 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: 51 51 52 -* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]] 53 -* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]] 54 -* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]] 57 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 55 55 56 56 == **Key takeaways** == 57 57 58 -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: 59 59 60 60 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 61 61 * If you have feedback or ideas for us, talk to the Platypus 62 -* 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. 63 63 * Clear your browser cache (Ctrl + Shift + Del) 64 64 * Check out the release notes [here] 65 65 * Start thinking about how the license tracker can aid your development ... ... @@ -72,6 +72,6 @@ 72 72 {{info}} 73 73 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 74 74 75 -~*~* Indicates a GEN3-only feature.78 +~*~* Indicates a next-generation-architecture only feature. 76 76 {{/info}})))((({{toc/}}))){{/container}} 77 77 {{/container}}