Skip to Content

Changes for page MQTT Connectivity

Last modified by Danniar Firdausy on 2024/05/21 11:24
From version 21.1
edited by Erik Bakker
on 2024/03/29 13:56
Change comment: There is no comment for this version
To version 22.1
edited by Danniar Firdausy
on 2024/05/16 16:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Active/Passive Failover
1 +MQTT Connectivity
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -7,10 +7,18 @@
7 7  == Documentation ==
8 8  
9 9  ==== 1. How to use====
10 -With the help of this store item, you can make the active/passive failover functionality possible within the runtime context.
10 +With the help of this store item, you can define your own MQTT broker to host MQTT topics on which external clients can publish messages and subscribe to for retrieving messages.
11 11  
12 12  ==== 2. Keynotes & restrictions====
13 13  
14 +Within eMagiz, we offer two implementations:
15 +
16 +1. To set this broker up to only accept MQTT messages
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 +
19 +2. To set up the broker to accept MQTT messages and AMQP messages
20 + 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"
21 +
14 14  * 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.
15 15  * 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.
16 16  * Each container needs a different port to communicate through.