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 7.2
edited by Danniar Firdausy
on 2024/09/03 08:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -40,7 +40,7 @@
40 40  
41 41  The above arguments concluded that the connectivity between eMagiz and the external system and the internal queue mechanism of eMagiz should be considered two separate things. This conclusion did raise a question on how eMagiz can guarantee message delivery. The messaging engine uses queues to ensure message delivery. But what if the first queue (the onramp queue) cannot be reached? What happens then.
42 42  
43 -The H2 database is introduced to safeguard against any problems within the entry. This component is generated in every entry in eMagiz. This H2 database will temporarily store data and act as a bridge between the entry and the onramp queue. This way, eMagiz can guarantee message delivery. If you want to learn more about the function of the H2 database, please check out this [microlearning](intermediate-solution-architecture-function-of-h2-database.md).
43 +The H2 database is introduced to safeguard against any problems within the entry. This component is generated in every entry in eMagiz. This H2 database will temporarily store data and act as a bridge between the entry and the onramp queue. This way, eMagiz can guarantee message delivery. If you want to learn more about the function of the H2 database, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.intermediate-solution-architecture-function-of-h2-database||target="blank"]].
44 44  
45 45  To summarize:
46 46  
... ... @@ -49,12 +49,8 @@
49 49  * Outside parties are not allowed to write on eMagiz queues directly
50 50  * eMagiz facilitates various connectivity methods (i.e., REST, SOAP, Database, File)
51 51  
52 -== 4. Assignment ==
52 +== 4. Key takeaways ==
53 53  
54 -No assignment accompanies this microlearning.
55 -
56 -== 5. Key takeaways ==
57 -
58 58  * The key aspects are:
59 59   ** Entry is the starting point of the integration process in messaging
60 60   ** Queues are an internal resource of eMagiz
... ... @@ -61,13 +61,12 @@
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 -== 6. Suggested Additional Readings ==
60 +== 5. Suggested Additional Readings ==
65 65  
66 -If you are interested in this topic, please boost your knowledge with the help of the internet.
62 +If you are interested in this topic and want more information on it please read the help text provided by eMagiz and read the following links:
67 67  
68 -== 7. Silent demonstration video ==
64 +* [[Entry (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22entry%22||target="blank"]]
65 +)))
69 69  
70 -As this is a more theoretical microlearning, we have no video for this.)))
71 -
72 72  ((({{toc/}}))){{/container}}
73 73  {{/container}}