Changes for page 57

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-61
	1	+58

Content

...	...	@@ -1,31 +1,52 @@
1		-Release that introduces a visual refresh on the Capture widget. 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.
4		-
5	5	Find out more in our [release blog]
6	6
7	7
8		-===== New features =====
	6	+===== New Features =====
9	9
10		-* Built-in support for EDI messages
11		- ** Design - System: EDI is a new message format supported in eMagiz. You can select this as the default option when editing a system or when editing a system message. Note that, this option is supported only for Generation 3 runtimes.
12		- ** Create - Flow designer: The autogenerated definitions and transformations components are customized so that EDI to XML validations and transformations are possible. Note that in this version the filter will not work with the eMagiz message definitions if they use multiple namespaces, in that case, a custom XSD should be used.
	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.
13	13
14	14	===== Minor Changes =====
15	15
16		-* Deploy - Releases: Improved performance for deploying releases using the deployment plan.
17		-* Capture - Requirements Designer: The requirements designer got a visual refresh. Furthermore, new (multi-tenant) systems can now be created by clicking the blue rectangles in the left panel, rather than by dragging them in.
18		-* Design - System Message Definition: Importing message definitions from store with multiple namespaces is supported.
19		-* Deploy - Releases. You are now able to prevent releases to be deleted (either by eMagiz or manually) by enabling the block autodeletion feature per release. This can be done for at most 3 releases in total. (#587)
20		-* Create - Flow designer: Improved the help texts of HTTP outbound components to clarify the exact working of the ‘encoding mode’ setting.
	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
21	21
	42	+===== Known Issues =====
22	22
23		-===== 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.
24	24
25		-* Deploy - Releases: We fix a small issue that adds an onramp (or an offramp) that is linked to an exit/entry connector to a release at a later moment. (#442)
26		-* Community - Q&A: The richtext editor no longer adds a break line when you change a style of text.
27		-* Create - Transformation: Fixed the position of the ‘View XSLT Button’ that in some cases was not correct.
28		-* Manage - Dashboard: The popup with detailed information on errors did not work for certain types of errors. (#583)
29		-* Deploy - Releases: You will not see an error in “Outdated Flows” pop-up if your release has outdated flows.
30		-* The help text is appearing correctly when clicking attributes on a page.
	46	+===== Remarks =====
31	31
	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.