Changes for page MQTT Connectivity

Summary

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

Details

Page properties

Content

...	...	@@ -13,18 +13,15 @@
13	13
14	14	Within eMagiz, we offer two implementations:
15	15
16		-1. To set this broker up to only accept MQTT messages
	16	+1. To set this MQTT broker up to only accept MQTT messages
17	17	Here, the benefit is that there are fewer components to manage in this flow. However, that also means it is impossible to transport your messages in the MQTT topics to an AMQP queue for further processing using eMagiz flows.
18		-1. To set up the broker to accept MQTT messages and AMQP messages
19		-If you need to further process the messages you receive from the MQTT broker using eMagiz flows, then you need to implement the second setup, which works by transporting the messages placed to the MQTT topics to an AMQP queue. If this is what you need, then please import another flow fragment called "MQTT Message Processing".
	18	+1. To set up the MQTT broker to accept MQTT messages and further process them using eMagiz flows
	19	+If you need to further process the messages you receive from the MQTT broker using eMagiz flows, then you can add this second setup into your flow, which works by transporting the messages placed to the MQTT topics to an AMQP queue. If this is what you need, then please import another flow fragment called "MQTT Message Processing".
20	20
21		-
22		-* Note that you also need to define the correct settings in each flow to group flows together that need to use the active/passive failover functionality.
23		-* When using this configuration you can only create groups within the context of a single runtime. So for each runtime for which you want this functionality you need to add this store item to the Infra flow.
24		-* Each container needs a different port to communicate through.
25		-* Each container needs their own cluster.
26		-* From Deploy you can control the failover functionality.
	21	+* Note that after you create a new version of your flow, before you create and deploy a new release, you also need to configure a new route in Deploy>Architecture of your desired environment for the clients (publishers and subscribers) of this MQTT broker to connect. The port that you define here, needs to be the same as the port that you define for your MQTT Broker in the flow that hosts it. See the image below as a reference:
27	27
	23	+[[image:Main.Images.Store.WebHome@store-accelerators-mqtt%20connectivity-deploy%20architecture%20routes.png]]
	24	+
28	28	==== 3. License Information====
29	29	Part of the standard license agreement as agreed upon when using the store for the first time.
30	30