Wiki source code of MQTT Connectivity
Version 28.1 by Danniar Firdausy on 2024/05/16 16:49
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
2.1 | 1 | {{container}} |
| 2 | {{container layoutStyle="columns"}} | ||
| |
4.1 | 3 | ((( |
| |
7.1 | 4 | == About == |
| |
20.1 | 5 | This store item can easily add the required configuration to your infra flow to make the active/passive failover functionality possible within the runtime context. |
| |
4.1 | 6 | |
| |
7.1 | 7 | == Documentation == |
| |
4.1 | 8 | |
| |
7.1 | 9 | ==== 1. How to use==== |
| |
22.1 | 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. |
| |
2.1 | 11 | |
| |
7.1 | 12 | ==== 2. Keynotes & restrictions==== |
| |
2.1 | 13 | |
| |
22.1 | 14 | Within eMagiz, we offer two implementations: |
| 15 | |||
| |
26.1 | 16 | 1. To set this MQTT broker up to only accept MQTT messages |
| |
23.1 | 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. |
| |
26.1 | 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". | ||
| |
25.1 | 20 | |
| |
26.1 | 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: |
| |
3.1 | 22 | |
| |
27.1 | 23 | [[image:Main.Images.Store.WebHome@store-accelerators-mqtt%20connectivity-deploy%20architecture%20routes.png]] |
| |
26.1 | 24 | |
| |
7.1 | 25 | ==== 3. License Information==== |
| |
15.1 | 26 | Part of the standard license agreement as agreed upon when using the store for the first time. |
| |
2.1 | 27 | |
| |
10.1 | 28 | ==== 4. Relevant eMagiz Academy Microlearnings==== |
| 29 | |||
| |
28.1 | 30 | * [[Routes Configuration>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.intermediate-emagiz-cloud-management-routes.WebHome||target="blank"]] |
| |
20.1 | 31 | * [[Deploy Possibilities>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-deploy-possibilities.WebHome||target="blank"]] |
| |
10.1 | 32 | |
| |
18.1 | 33 | //Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]]))) |
| |
2.1 | 34 | |
| 35 | |||
| |
3.1 | 36 | |
| |
11.1 | 37 | ((())) |
| |
2.1 | 38 | {{/container}} |
| 39 | {{/container}} |