Skip to Content

Changes for page Entry, not a queue

Last modified by Danniar Firdausy on 2024/09/16 13:40
From version 9.3
edited by Danniar Firdausy
on 2024/09/16 13:40
Change comment: There is no comment for this version
To version 9.4
edited by Danniar Firdausy
on 2024/09/16 13:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -11,14 +11,12 @@
11 11  
12 12  == 2. Key concepts ==
13 13  
14 -This microlearning centers on the concept of entry, not a queue.
14 +This microlearning centers on the concept of entry, not a queue. The key aspects are:
15 + * Entry is the starting point of the integration process in messaging
16 + * Queues are an internal resource of eMagiz
17 + * Outside parties are not allowed to write on eMagiz queues directly
18 + * eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
15 15  
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)
21 -
22 22  == 3. Entry, not a queue ==
23 23  
24 24  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.