Skip to Content

Changes for page Messaging Synchronous

Last modified by Danniar Firdausy on 2024/09/16 13:37
From version 10.1
edited by Erik Bakker
on 2023/01/23 08:37
Change comment: There is no comment for this version
To version 10.2
edited by Danniar Firdausy
on 2024/08/20 13:18
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
... ... @@ -32,7 +32,7 @@
32 32  * Messages have a time limit. The response needs to be back within 25 seconds (eMagiz default)
33 33  * Uses a request-response structure that talks to one system at a time
34 34  
35 -With this method, the sending party supplies the data to eMagiz via a push mechanism. eMagiz, in turn, places the data on a queue (in most cases an onramp queue). The subsequent process (the onramp) will process the message and will put the message on the next queue (the synchronous routing). That process will route each message to the correct offramp. This process continues until the message eMagiz delivers to the external system. At that point, eMagiz will wait for a response. If that response is received, the message will travel back to the starting point to deliver the reaction to the caller. If something goes wrong, for example, a timeout, the error message is also given back to the caller, and eMagiz will log the exception. If you want to learn more on that, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Understanding Error Handling.intermediate-understanding-error-handling-in-emagiz-messaging-synchronous||target="blank"]].
35 +With this method, the sending party supplies the data to eMagiz via a push mechanism. eMagiz, in turn, places the data on a queue (in most cases an onramp queue). The subsequent process (the onramp) will process the message and will put the message on the next queue (the synchronous routing). That process will route each message to the correct offramp. This process continues until the message eMagiz delivers to the external system. At that point, eMagiz will wait for a response. If that response is received, the message will travel back to the starting point to deliver the reaction to the caller. If something goes wrong, for example, a timeout, the error message is also given back to the caller, and eMagiz will log the exception. If you want to learn more on that, please check out this [[Messaging Asynchronous microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-messaging-messaging-asynchronous||target="blank"]].
36 36  
37 37  [[image:Main.Images.Microlearning.WebHome@intermediate-key-concepts-emagiz-messaging-messaging-synchronous--concept.png]]
38 38  
... ... @@ -71,11 +71,13 @@
71 71  
72 72  == 6. Suggested Additional Readings ==
73 73  
74 -If you are interested in this topic and want more information, please read the help text provided by eMagiz.
74 +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:
75 75  
76 -== 7. Silent demonstration video ==
76 +* [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
77 +** [[Crash Course Messaging (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.WebHome||target="blank"]]
78 +*** [[Messaging Asynchronous (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-messaging-messaging-asynchronous||target="blank"]]
77 77  
78 -As this is a more theoretical microlearning, we have no video for this.)))
80 +)))
79 79  
80 80  ((({{toc/}}))){{/container}}
81 81  {{/container}}