Changes for page Entry, not a queue

Summary

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

Details

Page properties

Author

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

Default language

...	...	@@ -1,1 +1,0 @@
1		-en

Content

...	...	@@ -5,6 +5,9 @@
5	5
6	6	Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7	7
	8	+* Last update: August 5th, 2021
	9	+* Required reading time: 5 minutes
	10	+
8	8	== 1. Prerequisites ==
9	9
10	10	* Intermediate knowledge of the eMagiz platform
...	...	@@ -14,20 +14,22 @@
14	14	This microlearning centers on the concept of entry, not a queue.
15	15
16	16	* The key aspects are:
17		- ** Entry is the starting point of the integration process in messaging
18		- ** Queues are an internal resource of eMagiz
19		- ** Outside parties are not allowed to write on eMagiz queues directly
20		- ** eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
	20	+ * Entry is the starting point of the integration process in messaging
	21	+ * Queues are an internal resource of eMagiz
	22	+ * Outside parties are not allowed to write on eMagiz queues directly
	23	+ * eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
21	21
	25	+
	26	+
22	22	== 3. Entry, not a queue ==
23	23
24	24	In this microlearning, we will explore what the function of the entry is within the message engine. Furthermore, we will explain why there is no entry queue.
25	25
26	26	* The key aspects are:
27		- ** Entry is the starting point of the integration process in messaging
28		- ** Queues are an internal resource of eMagiz
29		- ** Outside parties are not allowed to write on eMagiz queues directly
30		- ** eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
	32	+ * Entry is the starting point of the integration process in messaging
	33	+ * Queues are an internal resource of eMagiz
	34	+ * Outside parties are not allowed to write on eMagiz queues directly
	35	+ * eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
31	31
32	32	As you learned from the introductory course on messaging, we use a five-layer approach to handle data within the messaging engine. The first layer the data encounters is the entry. The goal of the entry is twofold. One is to establish a connection with an external system. The other is to place data on a queue. There are two ways to establish connectivity. The first method is via a pull mechanism. This pull mechanism means that eMagiz will initiate the communication to retrieve data. The second method is a push mechanism. This push mechanism means that eMagiz will patiently wait till the external system offers data to eMagiz. The push mechanism will typically be realized with the help of a hosted web service (REST or SOAP) within your eMagiz solution.
33	33
...	...	@@ -56,11 +56,13 @@
56	56	== 5. Key takeaways ==
57	57
58	58	* The key aspects are:
59		- ** Entry is the starting point of the integration process in messaging
60		- ** Queues are an internal resource of eMagiz
61		- ** Outside parties are not allowed to write on eMagiz queues directly
62		- ** eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
	64	+ * Entry is the starting point of the integration process in messaging
	65	+ * Queues are an internal resource of eMagiz
	66	+ * Outside parties are not allowed to write on eMagiz queues directly
	67	+ * eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
63	63
	69	+
	70	+
64	64	== 6. Suggested Additional Readings ==
65	65
66	66	If you are interested in this topic, please boost your knowledge with the help of the internet.
...	...	@@ -67,7 +67,9 @@
67	67
68	68	== 7. Silent demonstration video ==
69	69
70		-As this is a more theoretical microlearning, we have no video for this.)))
	77	+As this is a more theoretical microlearning, we have no video for this.
71	71
	79	+)))
	80	+
72	72	((({{toc/}}))){{/container}}
73	73	{{/container}}