Skip to Content

Changes for page Asynchronous Routing

Last modified by Danniar Firdausy on 2024/09/04 09:01
From version 20.1
edited by Erik Bakker
on 2022/08/15 08:05
Change comment: There is no comment for this version
To version 16.1
edited by Erik Bakker
on 2022/06/10 08:37
Change comment: Imported from XAR

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,0 @@
1 -Asynchronous Routing
Parent
... ... @@ -1,1 +1,0 @@
1 -WebHome
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,8 +1,13 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 += Asynchronous Routing =
3 +
2 2  In this microlearning, we will explain the basics of asynchronous routing that plays a vital role in the distribution of messages within the five-layer model of messaging.
3 3  
4 4  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
8 +* Last update: February 25th, 2021
9 +* Required reading time: 7 minutes
10 +
6 6  == 1. Prerequisites ==
7 7  
8 8  * Basic knowledge of the eMagiz platform
... ... @@ -18,6 +18,8 @@
18 18  * Based on a decision made within the routing the message is routed to one or more offramp queues
19 19  * Each offramp queue will receive data based on the decision unless you add another filter before the messages are sent to the offramp queue
20 20  
26 +
27 +
21 21  == 3. Asynchronous routing ==
22 22  
23 23  Asynchronous routing plays a crucial role in the distribution of messages it receives to one or more offramps.
... ... @@ -39,9 +39,9 @@
39 39  
40 40  This SpEL expression does the following things:
41 41  
42 -* It looks for the header called {technicalnameofproject}\_targetSystem and will split each entry based on the separator (a comma)
43 -* It will trim the result of this split and combine it the value in the header called {technicalnameofproject}\_messageType
44 -* For every unique combination it will search to a pre-configured list to see to which channel the message should be sent
49 +1. It looks for the header called {technicalnameofproject}\_targetSystem and will split each entry based on the separator (a comma)
50 +2. It will trim the result of this split and combine it the value in the header called {technicalnameofproject}\_messageType
51 +3. For every unique combination it will search to a pre-configured list to see to which channel the message should be sent
45 45  
46 46  In the standard router component this will look as follows:
47 47  
... ... @@ -110,6 +110,7 @@
110 110  [[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-asynchronous-routing--simple-asynchronous-routing-example.png]]
111 111  
112 112  
120 +
113 113  == 4. Assignment ==
114 114  
115 115  Build your asynchronous routing based on the best practice for one of the offramps that are available within your (Academy) project.
... ... @@ -121,6 +121,8 @@
121 121  * Control the output with a filter to prevent data to be sent to a queue too early
122 122  * Use the annotations to write down the step by step guide within your asynchronous routing
123 123  
132 +
133 +
124 124  == 6. Suggested Additional Readings ==
125 125  
126 126  If you are interested in this topic and want more information on it please read the help text provided by eMagiz.