Skip to Content

Changes for page Entry, not a queue

Last modified by Danniar Firdausy on 2024/09/16 13:40
From version 1.2
edited by eMagiz
on 2022/06/08 12:38
Change comment: Update document after refactoring.
To version 5.1
edited by Erik Bakker
on 2022/08/23 10:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -intermediate-key-concepts-emagiz-messaging-entry-not-a-queue
1 +Entry, not a queue
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.marijn
1 +XWiki.ebakker
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -1,20 +1,10 @@
1 -{{html wiki="true"}}
2 -<div class="ez-academy">
3 - <div class="ez-academy_body">
4 -
5 -<div class="doc">
6 -
7 -
8 -
9 -= Entry, not a queue =
10 -
1 +{{container}}
2 +{{container layoutStyle="columns"}}
3 +(((
11 11  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.
12 12  
13 -Should you have any questions, please get in touch with academy@emagiz.com.
6 +Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
14 14  
15 -* Last update: August 5th, 2021
16 -* Required reading time: 5 minutes
17 -
18 18  == 1. Prerequisites ==
19 19  
20 20  * Intermediate knowledge of the eMagiz platform
... ... @@ -24,22 +24,20 @@
24 24  This microlearning centers on the concept of entry, not a 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)
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)
31 31  
32 -
33 -
34 34  == 3. Entry, not a queue ==
35 35  
36 36  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.
37 37  
38 38  * The key aspects are:
39 - * Entry is the starting point of the integration process in messaging
40 - * Queues are an internal resource of eMagiz
41 - * Outside parties are not allowed to write on eMagiz queues directly
42 - * eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
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)
43 43  
44 44  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.
45 45  
... ... @@ -61,8 +61,6 @@
61 61  * Outside parties are not allowed to write on eMagiz queues directly
62 62  * eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
63 63  
64 -===== Practice =====
65 -
66 66  == 4. Assignment ==
67 67  
68 68  No assignment accompanies this microlearning.
... ... @@ -70,13 +70,11 @@
70 70  == 5. Key takeaways ==
71 71  
72 72  * The key aspects are:
73 - * Entry is the starting point of the integration process in messaging
74 - * Queues are an internal resource of eMagiz
75 - * Outside parties are not allowed to write on eMagiz queues directly
76 - * eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
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)
77 77  
78 -
79 -
80 80  == 6. Suggested Additional Readings ==
81 81  
82 82  If you are interested in this topic, please boost your knowledge with the help of the internet.
... ... @@ -83,11 +83,7 @@
83 83  
84 84  == 7. Silent demonstration video ==
85 85  
86 -As this is a more theoretical microlearning, we have no video for this.
70 +As this is a more theoretical microlearning, we have no video for this.)))
87 87  
88 -</div>
89 -
90 -</div>
91 -</div>
92 -
93 -{{/html}}
72 +((({{toc/}}))){{/container}}
73 +{{/container}}