Changes for page Asynchronous Routing
Last modified by Danniar Firdausy on 2024/09/04 09:01
From version 22.1
edited by Erik Bakker
on 2022/08/15 08:07
on 2022/08/15 08:07
Change comment:
There is no comment for this version
To version 37.4
edited by Danniar Firdausy
on 2024/08/20 15:34
on 2024/08/20 15:34
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.dfirdausy - Content
-
... ... @@ -35,7 +35,11 @@ 35 35 The best practice for setting up your asynchronous routing process is to use one SpEL expression that determines to which offramp queues a messages needs to be routed. 36 36 The SpEL expression looks as follows: 37 37 38 +{{code language="xml"}} 39 + 38 38 headers.{technicalnameofproject}\_targetSystem.split(',').![#this.trim()+#root.headers.{technicalnameofproject}_messageType] 41 + 42 +{{/code}} 39 39 40 40 This SpEL expression does the following things: 41 41 ... ... @@ -60,7 +60,7 @@ 60 60 61 61 === 3.2 Control output === 62 62 63 -As the asynchronous plays a role in routing messages between all asynchronous flows in the messaging solution you can imagine that making changes does not need to happen lightly. The other aspect is that when multiple projects are being built at the same time the asynchronous routing will house a multitude of changes that need to go to Acceptance or Production at the same time. 67 +As the asynchronous routing plays a role in routing messages between all asynchronous flows in the messaging solution you can imagine that making changes does not need to happen lightly. The other aspect is that when multiple projects are being built at the same time the asynchronous routing will house a multitude of changes that need to go to Acceptance or Production at the same time. 64 64 65 65 One control mechanism we consider a best practice to guard yourself against those risks is to add a filter before data is placed on the offramp queue. 66 66 By doing this consistently you can control when a specific offramp can receive data on any environment. In other words, when a certain system is not ready yet to receive data on Acceptance or Production but is ready on Test you can control this behavior with this solution. ... ... @@ -102,25 +102,21 @@ 102 102 [[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-asynchronous-routing--simple-asynchronous-routing-example.png]] 103 103 104 104 105 -== 4. Assignment ==109 +== 4. Key takeaways == 106 106 107 -Build your asynchronous routing based on the best practice for one of the offramps that are available within your (Academy) project. 108 -This assignment can be completed with the help of your (Academy) project you have created/used in the previous assignment. 109 - 110 -== 5. Key takeaways == 111 - 112 112 * Use one component that decides to route messages to certain channels 113 113 * Control the output with a filter to prevent data to be sent to a queue too early 114 114 * Use the annotations to write down the step by step guide within your asynchronous routing 115 115 116 -== 6. Suggested Additional Readings ==115 +== 5. Suggested Additional Readings == 117 117 118 118 If you are interested in this topic and want more information on it please read the help text provided by eMagiz. 119 119 120 -== 7. Silent demonstration video == 121 - 122 -This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned. 123 - 124 -{{video attachment="crashcourse-messaging-asynchronous-routing.mp4" reference="Main.Videos.Microlearning.WebHome"/}} 125 - 119 +* [[Store (Menu)>>doc:Main.eMagiz Store.WebHome||target="blank"]] 120 +** [[Accelerators (Navigation)>>doc:Main.eMagiz Store.Accelerators.WebHome||target="blank"]] 121 +*** [[Routing - SpEL (Store Item)>>doc:Main.eMagiz Store.Accelerators.Routing - SpEL.WebHome||target="blank"]] 122 +* [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] 123 +** [[Data traffic routing (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Data traffic routing.WebHome||target="blank"]] 124 +*** [[Synchronous routing (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Data traffic routing.intermediate-data-traffic-routing-synchronous-routing||target="blank"]] 125 +* [[Asynchronous Routing (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=%22asynchronous+routing%22||target="blank"]] 126 126 )))((({{toc/}}))){{/container}}{{/container}}