Skip to Content

Changes for page Asynchronous Routing

Last modified by Danniar Firdausy on 2024/09/04 09:01
From version 24.1
edited by Carlijn Kokkeler
on 2022/10/05 12:15
Change comment: There is no comment for this version
To version 22.1
edited by Erik Bakker
on 2022/08/15 08:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -34,10 +34,8 @@
34 34  
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 -{{code language=<providedlanguage>}}
37 +
38 38  headers.{technicalnameofproject}\_targetSystem.split(',').![#this.trim()+#root.headers.{technicalnameofproject}_messageType]
39 -{{/code}}
40 -headers.{technicalnameofproject}\_targetSystem.split(',').![#this.trim()+#root.headers.{technicalnameofproject}_messageType]
41 41  
42 42  This SpEL expression does the following things:
43 43  
... ... @@ -62,7 +62,7 @@
62 62  
63 63  === 3.2 Control output ===
64 64  
65 -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.
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.
66 66  
67 67  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.
68 68  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.