Changes for page MQTT Connectivity

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-MQTT Connectivity
	1	+Add Namespace

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.dfirdausy
	1	+XWiki.ebakker

Content

...	...	@@ -2,38 +2,27 @@
2	2	{{container layoutStyle="columns"}}
3	3	(((
4	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.
	5	+With the help of this transformation, you can easily add a namespace to your message. This is sometimes needed to communicate with an external system.
6	6
7	7	== Documentation ==
8	8
9	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.
	10	+With the help of this transformation, you can easily add a namespace to your message. This is sometimes needed to communicate with an external system.
11	11
12	12	==== 2. Keynotes & restrictions====
13	13
14		-Within eMagiz, we offer two implementations:
	14	+* Note that this is a custom XSLT that is designed for a specific cause.
	15	+* Always try to understand the context before you implement this transformation.
	16	+* Note that you need to define your specific namespace yourself when you want to implement this solution within your model.
15	15
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		-
19		-2. To set up the broker to accept MQTT messages and AMQP messages
20		-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"
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		-
28	28	==== 3. License Information====
29		-Part of the standard license agreement as agreed upon when using the store for the first time.
	19	+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.
30	30
31	31	==== 4. Relevant eMagiz Academy Microlearnings====
32	32
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	+None
35	35
36		-//Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]])))
	25	+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/?]])))
37	37
38	38
39	39