Skip to Content

Changes for page Entry, not a queue

Last modified by Danniar Firdausy on 2024/09/16 13:40
From version 5.1
edited by Erik Bakker
on 2022/08/23 10:16
Change comment: There is no comment for this version
To version 4.1
edited by Erik Bakker
on 2022/08/23 10:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,10 +14,10 @@
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)
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)
21 21  
22 22  == 3. Entry, not a queue ==
23 23  
... ... @@ -24,10 +24,10 @@
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)
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)
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,10 +56,10 @@
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)
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)
63 63  
64 64  == 6. Suggested Additional Readings ==
65 65