Skip to Content

Changes for page MQTT Connectivity

Last modified by Danniar Firdausy on 2024/05/21 11:24
From version 33.1
edited by Danniar Firdausy
on 2024/05/16 16:56
Change comment: There is no comment for this version
To version 35.1
edited by Danniar Firdausy
on 2024/05/21 11:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,7 +2,7 @@
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 4  == About ==
5 -This store item can accelerate you in seting up a MQTT Broker in your eMagiz flow with the minimum required configuration.
5 +This store item can accelerate you in setting up a MQTT Broker in your eMagiz flow with the minimum required configuration.
6 6  
7 7  == Documentation ==
8 8  
... ... @@ -18,7 +18,7 @@
18 18  1. To set up the MQTT broker to accept MQTT messages and further process them using eMagiz flows
19 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 -* 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:
21 +{{info}}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{{/info}}
22 22  
23 23  [[image:Main.Images.Store.WebHome@store-accelerators-mqtt%20connectivity-deploy%20architecture%20routes.png]]
24 24