Changes for page 217 - Template Tango

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-205 - World Explorers
	1	+217 - Template Tango

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,62 +1,52 @@
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!** 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	+**Hi there, eMagiz developers!** In this release, new cloud templates for docker single and double lane are introduced. These templates enable the ability to clean H2 databases from the portal. Next to this, it is now possible to edit the trigger "More than 100 messages on queue over 10 minutes". Moroever, serveral copy to clipboard buttons have been added. Lastly, the runtime overview has been improved with respect to checks on the runtime version.
6	6
7		-== ** Mandatory Cloud Template Upgrade - Next-generation models ** ==
	8	+== **Cloud Template R12 Docker - Single Lane** ==
	9	+This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here.
8	8
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.
	11	+== **Cloud Template R14 Docker - Double Lane** ==
	12	+This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here.
10	10
11	11	== **Feedback Items** ==
	15	+//__Custom trigger__//
	16	+The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger.
12	12
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.
	18	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
15	15
16		-{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
	20	+//__Copy to clipboard buttons__//
	21	+Copy to clipboard buttons have been added to various pages:
17	17
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	+ * Deploy agent pop-up
	24	+ * Create - Flow designer: Properties
	25	+ * Deploy - Property releases: Property details
20	20
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.
	27	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
23	23
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.
	29	+//__Reset H2 database__//
	30	+For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note the following:
26	26
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.
	32	+* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
	33	+* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime.
	34	+* For on-premise runtimes, only a reset of the runtime is needed.
29	29
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.
	36	+[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
36	36
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}}
38		-
39	39	== **Bug Fixes** ==
	39	+//__Runtime overview improvements__//
	40	+The runtime overview has been improved regarding checks on the runtime version.
40	40
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.
43		-
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.
46		-
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.
49		-
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.
52		-
53	53	== **Fancy Forum Answers** ==
54	54
55	55	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:
56	56
57		-* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
	46	+* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
	47	+* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
58	58
59		-== **Key takeaways** ==
	49	+== **Key Takeaways** ==
60	60
61	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:
62	62
...	...	@@ -67,7 +67,6 @@
67	67	* Check out the release notes [here]
68	68	* Start thinking about how the license tracker can aid your development
69	69	* Start thinking about major, minor, and patch
70		-* Upgrade to the latest build number
71	71	* Keep making great integrations
72	72
73	73	Let's stay in touch and till next time!
...	...	@@ -75,6 +75,11 @@
75	75	{{info}}
76	76	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77	77
78		-~*~* Indicates a next-generation-architecture only feature.
79		-{{/info}})))((({{toc/}}))){{/container}}
	67	+{{/info}}
	68	+)))
	69	+
	70	+(((
	71	+{{toc/}}
	72	+)))
80	80	{{/container}}
	74	+{{/container}}