Changes for page Asynchronous Routing

Last modified by Danniar Firdausy on 2024/09/04 09:01

From 17.2 to 17.1 From 37.11 to 37.10

From version 37.10

edited by Danniar Firdausy
on 2024/08/21 16:03

Change comment: There is no comment for this version

To version 17.2

edited by Erik Bakker
on 2022/06/13 11:19

Change comment: Update document after refactoring.

Raw
Rendered

Summary

Page properties (4 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--Asynchronous Routing
++crashcourse-messaging-asynchronous-routing

Author

@@ -1,1 +1,1 @@
--XWiki.dfirdausy
++XWiki.ebakker

Default language

...	...	@@ -1,1 +1,0 @@
1		-en

Content

@@ -1,8 +1,13 @@
  {{container}}{{container layoutStyle="columns"}}(((
--In this microlearning, we will dive into the essentials of asynchronous routing and its importance in managing message distribution within the five-layer messaging model. We will cover the key concepts, including how to route messages efficiently and manage output control.
++= Asynchronous Routing =
--If you have any questions along the way, feel free to reach out to us at [[academy@emagiz.com>>mailto:academy@emagiz.com]].
++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.
++Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
++
++* Last update: February 25th, 2021
++* Required reading time: 7 minutes
++
  == 1. Prerequisites ==
  * Basic knowledge of the eMagiz platform
@@ -10,16 +10,26 @@
  == 2. Key concepts ==
  This microlearning centers around asynchronous routing for messaging flows in eMagiz.
--* With asynchronous routing we mean: The process that routes messages that it receives to the correct outbound queue based on some metadata.
++By asynchronous routing we mean: The process that routes messages that it receives to the correct outbound queue based on some metadata.
++The asynchronous routing has three relevant parts:
++
++* All asynchronous onramps send their data to the routing
++* Based on a decision made within the routing the message is routed to one or more offramp queues
++* Each offramp queue will receive data based on the decision unless you add another filter before the messages are sent to the offramp queue
++
++
++
  == 3. Asynchronous routing ==
--Asynchronous routing plays a crucial role in the distribution of messages it receives to one or more offramps. In eMagiz, the asynchronous routing has three relevant parts:
++Asynchronous routing plays a crucial role in the distribution of messages it receives to one or more offramps.
--* All asynchronous onramps that send data to the routing.
--* Based on a decision made within the routing the message is routed to one or more offramp queues.
--* Each offramp queue will receive data based on the decision unless you add another filter before the messages are sent to the offramp queue.
++The asynchronous routing has three relevant parts:
++* All asynchronous onramps send their data to the routing
++* Based on a decision made within the routing the message is routed to one or more offramp queues
++* Each offramp queue will receive data based on the decision unless you add another filter before the messages are sent to the offramp queue
++
  === 3.1 Make a decision ===
  In asynchronous routing, you can build your decision model on which the routing needs to make the decision.
@@ -27,17 +27,13 @@
  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.
  The SpEL expression looks as follows:
--{{code language="xml"}}
--
  headers.{technicalnameofproject}\_targetSystem.split(',').![#this.trim()+#root.headers.{technicalnameofproject}_messageType]
--{{/code}}
--
  This SpEL expression does the following things:
--* It looks for the header called {technicalnameofproject}\_targetSystem and will split each entry based on the separator (a comma)
--* It will trim the result of this split and combine it the value in the header called {technicalnameofproject}\_messageType
--* For every unique combination it will search to a pre-configured list to see to which channel the message should be sent
++1. It looks for the header called {technicalnameofproject}\_targetSystem and will split each entry based on the separator (a comma)
++2. It will trim the result of this split and combine it the value in the header called {technicalnameofproject}\_messageType
++3. For every unique combination it will search to a pre-configured list to see to which channel the message should be sent
  In the standard router component this will look as follows:
@@ -56,10 +56,16 @@
  === 3.2 Control output ===
--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.
++As the asynchronous plays a role in routing messages between all asynchronous flows in a
++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.
--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.
--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.
++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.
++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.
  Below you see how this will look on flow level.
@@ -78,17 +78,19 @@
  Steps to follow when adding an integration to the routing Part I:
--* Add a header in the onramp named {technicalnameofproject}\_targetSystem (if this is not done yet)
--* Fill this header with a value that should be defined as a property (naming convention = systemname.messagetype.targetsystems)
--* This property should be created in Test, Accp, and Prod and filled with all target systems for a certain message type (notation = systemname1,systemname2,systemname3)
--* In the routing a standard router should be used as the first building block after receiving the input.
++1. Add a header in the onramp named {technicalnameofproject}\_targetSystem (if this is not done yet)
++2. Fill this header with a value that should be defined as a property (naming convention = systemname.messagetype.targetsystems)
++3. This property should be created in Test, Accp, and Prod and filled with all target systems for a certain message type (notation = systemname1,systemname2,systemname3)
++4. In the routing a standard router should be used as the first building block after receiving the input.
  Part II
--* In this standard router a SpelExpression has to be defined **once** that concatenates the following headers: {technicalnameofproject}\_targetSystem and {technicalnameofproject}\_messageType.
--* For every unique combination there is a value that should be specified alongside the channel on which to put the message (this should be a channel that ultimately leads to the correct offramp queue)
--* For every channel that leads to a JMS outbound channel adapter a filter needs to be added to make sure that each output option can be turned on or off easily. This to prevent that messages are sent to a system that does not expect them then
--* This filter should look like this: '${routing.monitor.detorem.enabled}' == 'true'. The naming convention of said property is routing.targetsystem.messagetype.enabled.
++5. In this standard router a SpelExpression has to be defined **once** that concatenates the following headers: {technicalnameofproject}\_targetSystem and {technicalnameofproject}\_messageType.
++6. For every unique combination there is a value that should be specified alongside the channel on which to put the message (this should be a channel that ultimately leads to the correct offramp queue)
++7. For every channel that leads to a JMS outbound channel adapter a filter needs to be added to make sure that each output option can be turned on or off easily.
++   This to prevent that messages are sent to a system that does not expect them then
++   8 This filter should look like this: '${routing.monitor.detorem.enabled}' == 'true'.
++   The naming convention of said property is routing.targetsystem.messagetype.enabled.
  === 3.5 The result ===
@@ -98,21 +98,28 @@
  [[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-asynchronous-routing--simple-asynchronous-routing-example.png]]
--== 4. Key takeaways ==
++== 4. Assignment ==
++
++Build your asynchronous routing based on the best practice for one of the offramps that are available within your (Academy) project.
++This assignment can be completed with the help of your (Academy) project you have created/used in the previous assignment.
++
++== 5. Key takeaways ==
++
  * Use one component that decides to route messages to certain channels
  * Control the output with a filter to prevent data to be sent to a queue too early
  * Use the annotations to write down the step by step guide within your asynchronous routing
--== 5. Suggested Additional Readings ==
--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 link:
--* [[Store (Menu)>>doc:Main.eMagiz Store.WebHome||target="blank"]]
--** [[Accelerators (Navigation)>>doc:Main.eMagiz Store.Accelerators.WebHome||target="blank"]]
--*** [[Routing - SpEL (Store Item)>>doc:Main.eMagiz Store.Accelerators.Routing - SpEL.WebHome||target="blank"]]
--* [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
--** [[Data traffic routing (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Data traffic routing.WebHome||target="blank"]]
--*** [[Synchronous routing (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Data traffic routing.intermediate-data-traffic-routing-synchronous-routing||target="blank"]]
--* [[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"]]
++== 6. Suggested Additional Readings ==
++
++If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
++
++== 7. Silent demonstration video ==
++
++This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
++
++{{video attachment="crashcourse-messaging-asynchronous-routing.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
++
  )))((({{toc/}}))){{/container}}{{/container}}