Skip to Content

Changes for page MQTT Connectivity

Last modified by Danniar Firdausy on 2024/05/21 11:24
From version 8.1
edited by Erik Bakker
on 2022/05/02 09:31
Change comment: There is no comment for this version
To version 25.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 -SOAP Web service Connectivity
1 +MQTT Connectivity
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -2,40 +2,41 @@
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 4  == About ==
5 -This store element will allow you to create an easy connection to SOAP based web services. XML data can be send to these web services, and for each connectivity type there is a Flow Fragment available.
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 -Ensure to locate the right connectivity method and import the right flow fragment.
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 -* These flow fragments will contain only the eMagiz components to make a call to a SOAP based webservice.
15 -* The basic authentication flow fragment requires empty key and trust store that are to be added separately. These are not included in this store component.
14 +Within eMagiz, we offer two implementations:
16 16  
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 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".
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.
27 +
17 17  ==== 3. License Information====
18 18  Part of the standard license agreement as agreed upon when using the store for the first time.
19 19  
20 20  ==== 4. Relevant eMagiz Academy Microlearnings====
21 -[[https:~~/~~/emagiz.github.io/docs/microlearning/novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice>>url:https://emagiz.github.io/docs/microlearning/novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice]]
22 22  
33 +* [[Flow Configuration>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-flow-configuration.WebHome||target="blank"]]
34 +* [[Deploy Possibilities>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-deploy-possibilities.WebHome||target="blank"]]
23 23  
24 -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/?]])))
36 +//Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]])))
25 25  
26 26  
27 27  
28 -((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
29 -|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option
30 -|(% style="width:45px" %) a|(% style="width:241px" %) Basic Authentication
31 -|(% style="width:45px" %) b|(% style="width:241px" %) WS Addressing - Call back
32 -|(% style="width:45px" %) c|(% style="width:241px" %) Client certificate
33 -|(% style="width:45px" %) d|(% style="width:241px" %) Mapped headers
34 -|(% style="width:45px" %) e|(% style="width:241px" %) Token based - static
35 -|(% style="width:45px" %) f|(% style="width:241px" %) Token based - dynamic
36 -|(% style="width:45px" %) g|(% style="width:241px" %) SSL
37 -|(% style="width:45px" %) h|(% style="width:241px" %) No authentication
38 -|(% style="width:45px" %) i|(% style="width:241px" %) Dynamic URL
39 -)))
40 +((()))
40 40  {{/container}}
41 41  {{/container}}