Skip to Content

Changes for page MQTT Connectivity

Last modified by Danniar Firdausy on 2024/05/21 11:24
From version 9.1
edited by Erik Bakker
on 2022/05/02 09:34
Change comment: There is no comment for this version
To version 24.1
edited by Danniar Firdausy
on 2024/05/16 16:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -eMagiz Data Sink
1 +MQTT Connectivity
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -2,31 +2,43 @@
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 4  == About ==
5 -With the help of this functionality, you can sink your messages into the eMagiz data sink bucket. Once the message is stored in the eMagiz data sink bucket, you will have the option to view this message in the Manage phase.
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.
6 6  
7 7  == Documentation ==
8 8  
9 9  ==== 1. How to use====
10 -Once stored, eMagiz can retrieve all messages with the same ID attached during the sink action via the Manage phase. In this case, it is assumed that your eMagiz data sink is such that you can review them on the fly. Other eMagiz data sink variants are offered that required specific on-demand queries.
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 -* Note that you should think about when you want to archive your data to the eMagiz data sink. That choice determines what the impact on the functional flow is.
15 -* Don't use a wiretap to invoke this part of the flow, as that causes the sink's behavior to happen before the actual processing. If the sink fails, the message will not be delivered via the functional part of the flow.
16 -* Note that we define (among others) how the message is stored in the data sink bucket in this component. The file structure expression should not be altered, as changing this would break the functionality.
17 -* Note that the 'standard' eMagiz headers to define the source system (i.e. relevant systems) and the messageType need to be available upon sinking to make this functionality work.
14 +Within eMagiz, we offer two implementations:
18 18  
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 +1. To set this broker up to only accept MQTT messages
19 +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.
20 +
21 +2. To set up the broker to accept MQTT messages and AMQP messages
22 +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"
23 +
24 +* 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.
25 +* 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.
26 +* Each container needs a different port to communicate through.
27 +* Each container needs their own cluster.
28 +* From Deploy you can control the failover functionality.
29 +
19 19  ==== 3. License Information====
20 -To use this store item you need to secure an additional license on the eMagiz platform. If you are interested in such a license please contact us at productmanagement@emagiz.com.
31 +Part of the standard license agreement as agreed upon when using the store for the first time.
21 21  
22 -Would you please consult the privacy policy of eMagiz at the following link: [[https:~~/~~/www.emagiz.com/privacy-policy/?>>url:https://www.emagiz.com/privacy-policy/?]])))
33 +==== 4. Relevant eMagiz Academy Microlearnings====
23 23  
35 +* [[Flow Configuration>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-flow-configuration.WebHome||target="blank"]]
36 +* [[Deploy Possibilities>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-deploy-possibilities.WebHome||target="blank"]]
24 24  
38 +//Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]])))
25 25  
26 -((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
27 -|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option
28 -|(% style="width:45px" %) a|(% style="width:241px" %) XML message(s)
29 -|(% style="width:45px" %) b|(% style="width:241px" %) JSON Message(s)
30 -)))
40 +
41 +
42 +((()))
31 31  {{/container}}
32 32  {{/container}}