Changes for page R13 - Double Lane

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Feedback Fiesta
	1	+58

Parent

...	...	@@ -1,1 +1,1 @@
1		-Main.Release Information.Portal.WebHome
	1	+Main.Release Information.Build numbers.WebHome

Content

...	...	@@ -1,60 +1,52 @@
1		-Release that improves the usability of the UI. Furthermore, we have some improvements on the MFA configuration. In addition, this release includes several other improvements, and tackles some minor issues.
	1	+Update that improves the AMQP and MQTT messaging capabilities.
2	2
3		-To benefit from the improvements, please make sure to clear your browser cache (Ctrl+Shift+Del) before signing in the first time.
	3	+Find out more in our [release blog]
4	4
5		-Find out more on our release blog here:
6		-https://www.emagiz.com/en/release-blog-en/174-feedback-fiesta-release-blog/
7	7
	6	+===== New Features =====
8	8
9		-===== Runtime Release Notes =====
	8	+* With this update, eMagiz runtimes can fulfil the role of an MQTT broker. To do this, put an Artemis server support object in your connector and make sure it accepts MQTT protocol communication over web sockets. Internally, handling these (MQTT) messages is no different from handling "normal" (AMQP) messages.
	9	+* Updated Artemis, Qpid, Proton-J and Netty to the latest maintenance releases. These updates mostly contain bugfixes, improvements and performance wins.
10	10
11		-The 5.1.0 release of the eMagiz Mendix connector (EMC) has two small bug fixes and updates most of the userlib libraries to include the latest security fixes. For specific information please check out this link to the [release notes]
12		-
13		-
14		-===== Major Changes =====
15		-
16		-* The UI has gotten several improvements for usability.
17		-* Portal: After logging in, users who have not configured MFA will be prompted with the page for setting up the Google Authenticator. Users who do not configure it will not be allowed to access anything until they follow the procedure.
18		-
19		-
20	20	===== Minor Changes =====
21	21
22		-* Design - Architecture: Added help text on the Gen3 attribute of the container.
23		-* Design - CDM: You cannot import models from Mendix in CDM from now on.
24		-* Design - API Catalog: A confirmation pop-up will popup on the screen when you do a deletion of resources. (#613)
25		-* Create - Processes: The tags were not being ordered in any way, and now they are being ordered alphabetically for it to be easier to search for them. (#346)
26		-* Create - Flow testing: A message pop-up can be used to see your input message even if you have not defined an expected message. (#599)
27		-* Deploy - Releases: The release attribute to prevent deletion of the release can be edited if the release is locked.
28		-* Deploy - Architecture: Name change of the Status tab on the runtime popup.
29		-* Deploy - Architecture: Improved feedback when trying to deploy Gen3 runtimes to offline machines.
30		-* Deploy - Event Streaming: The event streaming tab in the Deploy phase has been removed. (#542)
31		-* Deploy - User management: Access key, access certificate, and Keystore filenames are generated with the corresponding deploy user’s name. (#426)
32		-* Manage - Dashboard: A new button “Refresh“ is added to the right panel of the Dashboard. It helps you to refresh a view and update the errors in the meantime. (#589)
33		-* Manage - Monitoring: Gen3 monitoring pages merged with the Gen2 monitoring pages.
34		-* Portal: Improved the auto-generation of technical names by only removing the vowels if the length limit requires it. (#339)
35		-* MFA: You can type in your MFA code and press enter key to validate your code. (#132)
36		-* License tracker: On-premises and Data sink (Cloud) information removed. (#611)
37		-* Capture - Consumer API integration: Improved name validation when adding a new consumer API integration.
38		-* Design - API management: Finding resources in the Catalog API is easier from now on. The list has been sorted by a resource's path. (#607)
39		-* Design - System Message: a progress bar will be shown when the root of the message is changing. (#534)
40		-* Design - Consumer API Integration: Improved functionality for enabling consumer API Integration.
	13	+* Added bundle 'com.emagiz.bundles.artemis-quorum-api' 2.19.0.1
	14	+* Added bundle 'com.emagiz.bundles.netty-handler-proxy' 4.1.70.1
	15	+* Added bundle 'com.emagiz.bundles.netty-transport-classes-epoll' 4.1.70.1
	16	+* Added bundle 'com.emagiz.bundles.netty-transport-classes-kqueue' 4.1.70.1
	17	+* Updated bundle 'com.emagiz.bundles.artemis-server-osgi' from 2.7.0.2 to 2.19.0.1
	18	+* Updated bundle 'com.emagiz.bundles.netty-buffer' from 4.1.50.1 to 4.1.70.1
	19	+* Updated bundle 'com.emagiz.bundles.netty-codec' from 4.1.50.1 to 4.1.70.1
	20	+* Updated bundle 'com.emagiz.bundles.netty-codec-http' from 4.1.50.1 to 4.1.70.1
	21	+* Updated bundle 'com.emagiz.bundles.netty-codec-mqtt' from 4.1.50.1 to 4.1.70.1
	22	+* Updated bundle 'com.emagiz.bundles.netty-codec-socks' from 4.1.50.1 to 4.1.70.1
	23	+* Updated bundle 'com.emagiz.bundles.netty-common' from 4.1.50.1 to 4.1.70.1
	24	+* Updated bundle 'com.emagiz.bundles.netty-handler' from 4.1.50.1 to 4.1.70.1
	25	+* Updated bundle 'com.emagiz.bundles.netty-resolver' from 4.1.50.1 to 4.1.70.1
	26	+* Updated bundle 'com.emagiz.bundles.netty-transport' from 4.1.50.1 to 4.1.70.1
	27	+* Updated bundle 'com.emagiz.bundles.netty-transport-native-epoll' from 4.1.50.1 to 4.1.70.1
	28	+* Updated bundle 'com.emagiz.bundles.netty-transport-native-kqueue' from 4.1.50.1 to 4.1.70.1
	29	+* Updated bundle 'com.emagiz.bundles.netty-transport-native-unix-common' from 4.1.50.1 to 4.1.70.1
	30	+* Updated bundle 'com.emagiz.bundles.proton-j' from 0.33.5.1 to 0.33.10.1
	31	+* Updated bundle 'com.emagiz.bundles.qpid-jms-client' from 0.48.0.1 to 0.59.0.1
	32	+* Updated bundle 'com.emagiz.components.artemis' from 2.0.0 to 2.0.1
	33	+* Updated bundle 'com.emagiz.components.qpid' from 2.0.0 to 2.0.1
	34	+* Replaced bundle 'org.apache.activemq.artemis-amqp-protocol' 2.7.0 with 'com.emagiz.bundles.activemq-artemis-native' 2.19.0.1
	35	+* Replaced bundle 'org.apache.activemq.artemis-hornetq-protocol' 2.7.0 with 'com.emagiz.bundles.artemis-hornetq-protocol' 2.19.0.1
	36	+* Replaced bundle 'org.apache.activemq.artemis-hqclient-protocol' 2.7.0 with 'com.emagiz.bundles.artemis-hqclient-protocol' 2.19.0.1
	37	+* Replaced bundle 'org.apache.activemq.artemis-mqtt-protocol' 2.7.0 with 'com.emagiz.bundles.artemis-mqtt-protocol' 2.19.0.1
	38	+* Replaced bundle 'org.apache.activemq.artemis-native' 1.0.0 with 'com.emagiz.bundles.activemq-artemis-native' 1.0.2.1
	39	+* Replaced bundle 'org.apache.activemq.artemis-stomp-protocol' 2.7.0 with 'com.emagiz.bundles.artemis-stomp-protocol' 2.19.0.1
	40	+* Replaced bundle 'org.apache.johnzon.core' 0.9.5 with 'com.emagiz.bundles.johnzon-core' 1.2.15.1
41	41
	42	+===== Known Issues =====
42	42
43		-===== Bug Fixes =====
	44	+* Retrying to deliver a message from the dead-letter queue does not work, breaking the message redelivery feature. This is fixed in build 59.
44	44
45		-* Design - Solution: It is possible to go to response message mapping from the context menu. (#587)
46		-* Design - Processors: The list of event streaming topics will be sorted alphabetically when you create or edit the event processors. (#568)
47		-* Create - Flow Designer: In the popup, the comparator of messages will take all the available space. (#483)
48		-* Create - Flow designer: A wrong description of the XML validating filter component has been removed. (#567)
49		-* Create - Flow testing: When testing flows with multiple output messages (by using splitters) the result always showed “failure” even though visually the expected and actual messages appeared to be 100% identical. This has been fixed: if all messages are identical and in the same order, the result is “success” as you’d expect. (#454)
50		-* Create - Flow testing: We align some buttons at the bottom of the Flow designer and Flow testing.
51		-* Create - Flow testing: We displayed 3 missing buttons (Test messages, Build flow, and Help) on the Flow testing again.
52		-* Create - Flow testing: We fixed an issue where flows that contain debug components could not be tested.
53		-* Deploy - Releases: Creating a new release is easier. You only need to press once to select or change a flow version. (#594)
54		-* Deploy - Architecture: We fixed a bug where upgrading to the latest Gen3 cloud release caused JMS connectivity issues.
55		-* Deploy - Architecture: Improved Route generation so the streaming container will no longer be added to the existing gateway routes. If you encountered this bug, please remove the streaming container from your gateway routes and delete the 'entry.port' property created for the streaming container.
56		-* Deploy - Containers: The gateway entry flow will not be randomly added to the streaming container anymore. (#578)
57		-* Manage - Topic Statistics: Navigating to topic statistics does not show an error message if you have not authenticated your MFA yet. (#376)
58		-* eMagiz Mendix connector: Version 5.1.0 fixes the String-only functionality of synchronous exit configurations. We also updated the user lib dependencies to bring them in line with build 60. (#536)
59		-* Deploy - Releases: Build version is not being displayed multiple times when hovering over the integrations in the releases screen. (#513)
	46	+===== Remarks =====
60	60
	48	+* When upgrading a JMS server flow, the persisted messages stored in the Artemis server are automatically migrated from version 2.7.0 to 2.19.0 to guarantee a smooth upgrade process without any message loss. However, this migration process is irreversible, meaning that if for any reason you want to "downgrade" from 2.19.0 to 2.7.0 you must first use the "clean store" functionality in the deploy phase (cloud) or manually empty the Artemis 'data' directory (on-premises).
	49	+* Because of the above, if you are upgrading a failover setup (double lane), make sure to do the upgrade in the correct order for the live and backup JMS servers:
	50	+ ** Install the new build number (58) on both the live and backup servers.
	51	+ ** Start the new flow on the backup server first, and when that has finished start the new flow on the live server. This step automatically migrates everything in the Artemis 'data' directory (see above).
	52	+ ** When everything runs correctly again, uninstall the old flow from the backup server first and then uninstall it from the live server. While uninstalling you might notice some disruptions in the log: this is expected and should only last for a few seconds.