Skip to Content

Changes for page 217 - Template Tango

Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 94.1
edited by Erik Bakker
on 2023/06/22 13:26
Change comment: There is no comment for this version
To version 108.1
edited by Carlijn Kokkeler
on 2023/09/18 11:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -200 - Uncharted Territories
1 +205 - World Explorers
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,27 +1,71 @@
1 -In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture and others.
1 +{{container}}
2 +{{container layoutStyle="columns"}}(((
3 +[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.200 - Uncharted Territories.WebHome||target= "blank"]].
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.
4 4  
5 -=====Minor changes=====
7 +== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
6 6  
7 -* Create - Flow Designer: it is possible to select multiple components by area selection on the area with a scrollbar.
8 -* Create - Flow designer: The new best practices have updated Kafka components' default values. Updated values are:
9 -** For Kafka templates:
10 -*** Batch size: 200000
11 -*** Linger: 300
12 -** For Kafka message listener containers
13 -*** Fetch min. amount: 100000
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.
14 14  
11 +== **Feedback Items** ==
15 15  
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.
16 16  
17 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
18 -* Deploy - Architecture: We removed the deprecated reminder popup to update your cloud slot template. The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture.
19 -* Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation. Now, you can see all related logs regarding your deployment. By default, we only show some necessary logs, such as error logs, warning logs, and started runtime information logs. You can use the filter logs icons at the top of the list to show more information.
20 -* Deploy - Deployment plan: We updated the logic within our deployment plan functionality. The deployment step that disables all enabled triggers from the Manage phase disables triggers till you exit the deployment plan overview. That means that those triggers will be re-enabled after you move away from the deployment process or close the browser. Furthermore, there is no deployment step configuration to "enable" triggers anymore.
16 +{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
21 21  
22 -====Bug fixes====
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.
23 23  
24 -* Deploy - Architecture: We improved timeout settings to give Stop, Restart, and Reset runtime actions enough time to execute. (#957)
25 -* Design - Store: Importing into "Design" from the store is possible, even if the integration is not in Create yet.
26 -* Manage - Monitoring: Detailed HTTP statistics will now show the correct user in case of API key authorization in more cases. Note that this functionality requires a newly deployed release. (#956)
27 -* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
21 +//__Show values on the runtime level in Deploy Architecture__//
22 +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.
23 +
24 +{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
25 +* JMS - The number of queues in the active release.
26 +* Messaging Container - The number of messaging integrations in the active release.
27 +* Messaging Connector - The number of messaging integrations related to this system in the active release.
28 +* API Gateway Container - The number of operations in the active release.
29 +* Event Streaming Container - The number of event processors in the active release.
30 +
31 +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}}
32 +
33 +== **Bug Fixes** ==
34 +
35 +//__Gain the ability again to configure certificates in Deploy Architecture again__//
36 +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.
37 +
38 +//__Ensure that differing container configurations deploy the correct configuration__//
39 +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.
40 +
41 +//__Remove queurying options in Manage__//
42 +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.
43 +
44 +== **Fancy Forum Answers** ==
45 +
46 +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:
47 +
48 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
49 +
50 +== **Key takeaways** ==
51 +
52 +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:
53 +
54 +* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
55 +* If you have feedback or ideas for us, talk to the Platypus
56 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
57 +* Clear your browser cache (Ctrl + Shift + Del)
58 +* Check out the release notes [here]
59 +* Start thinking about how the license tracker can aid your development
60 +* Start thinking about major, minor, and patch
61 +* Upgrade to the latest build number
62 +* Keep making great integrations
63 +
64 +Let's stay in touch and till next time!
65 +
66 +{{info}}
67 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
68 +
69 +~*~* Indicates a next-generation-architecture only feature.
70 +{{/info}})))((({{toc/}}))){{/container}}
71 +{{/container}}