Skip to Content

Changes for page MQTT Connectivity

Last modified by Danniar Firdausy on 2024/05/21 11:24
From version 26.1
edited by Danniar Firdausy
on 2024/05/16 16:41
Change comment: There is no comment for this version
To version 6.1
edited by Erik Bakker
on 2022/05/02 08:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -MQTT Connectivity
1 +SOAP Web service Connectivity
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -1,39 +1,40 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 -== About ==
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 += 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.
6 6  
7 -== Documentation ==
7 += Documentation =
8 8  
9 -==== 1. How to use====
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.
9 +**~1. How to use**
10 +Ensure to locate the right connectivity method and import the right flow fragment.
11 11  
12 -==== 2. Keynotes & restrictions====
12 +**2. Keynotes & restrictions **
13 13  
14 -Within eMagiz, we offer two implementations:
14 +a. These flow fragments will contain only the eMagiz components to make a call out to the SOAP based webservice - These components do not hold any system messages - 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.
15 15  
16 -1. To set this MQTT 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 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".
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:
22 -
23 -
24 -
25 -==== 3. License Information====
16 +**3. License Information**
26 26  Part of the standard license agreement as agreed upon when using the store for the first time.
27 27  
28 -==== 4. Relevant eMagiz Academy Microlearnings====
19 +**4. Relevant eMagiz Academy Microlearnings**
20 +[[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]]
29 29  
30 -* [[Flow Configuration>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-flow-configuration.WebHome||target="blank"]]
31 -* [[Deploy Possibilities>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-deploy-possibilities.WebHome||target="blank"]]
32 32  
33 -//Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]])))
23 +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/?]])))
34 34  
35 35  
36 36  
37 -((()))
27 +((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
28 +|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option
29 +|(% style="width:45px" %) a|(% style="width:241px" %) Basic Authentication
30 +|(% style="width:45px" %) b|(% style="width:241px" %) WS Addressing - Call back
31 +|(% style="width:45px" %) c|(% style="width:241px" %) Client certificate
32 +|(% style="width:45px" %) d|(% style="width:241px" %) Mapped headers
33 +|(% style="width:45px" %) e|(% style="width:241px" %) Token based - static
34 +|(% style="width:45px" %) f|(% style="width:241px" %) Token based - dynamic
35 +|(% style="width:45px" %) g|(% style="width:241px" %) SSL
36 +|(% style="width:45px" %) h|(% style="width:241px" %) No authentication
37 +|(% style="width:45px" %) i|(% style="width:241px" %) Dynamic URL
38 +)))
38 38  {{/container}}
39 39  {{/container}}