Developing Business Rules
Debugging Routing Rules
This chapter describes how to test routing rules without sending the message through the entire production. It also contains flow diagrams that can help you debug problems in routing rules defined for EDI messages in a production.
Using the Test
tab of the Rule Editor, you can see whether a message triggers any of the routing rules without having to send the message through the entire production. Running this test does not transform or send the message, but any functions in the condition are executed as if the message ran through the production.
If you want to test a rule’s constraint that is based on the source of the message, use the Production source for test
field to specify the business host in the production that is sending the message. You can click the Select
button to choose the business host from a list.
You can test a routing rule by pasting the raw text of a message into the test tool. To do so:
This section describes strategies for debugging the routing rules in an EDI message routing production.
The primary symptom for problems in routing rules is that the message does not reach its destination. Perhaps the message reaches a point along the way, such as a business operation or routing process within the routing production, but it does not reach its target destination, which is generally an application server outside InterSystems IRIS™. In that case you can follow the problem-solving sequence captured in the next four drawings: “Solving Problems with Routing Rules,” Drawings A
, and D
Solving Problems with Routing Rules (Drawing A)
Solving Problems with Routing Rules (Drawing B)
Solving Problems with Routing Rules (Drawing C)
Solving Problems with Routing Rules (Drawing D)
Content Date/Time: 2019-05-14 12:01:37