CA API Gateway 9.1

9.4 9.1

Execute Routing Strategy Assertion

The Execute Routing Strategy assertion is the second part of the dynamic routing capability. It takes the chosen routing strategy from the ${<strategyPrefix>} variable populated by the Create Routing Strategy assertion, acquires a route destination and places it in a new route variable.
gateway83
The Execute Routing Strategy assertion is the second part of the dynamic routing capability. It takes the chosen routing strategy from the ${<
strategyPrefix
>} variable populated by the Create Routing Strategy assertion, acquires a route destination and places it in a new route variable.
Before you can execute a routing strategy, create a route first, through the Create Routing Strategy Assertion. See Working with Dynamic Routing Strategy before creating a route. The Create Routing Strategy assertion must precede Execute Routing Strategy.
Context Variables Created by This Assertion
The Execute Routing Strategy assertion sets the following context variables:
Variable
Description
${<
route
>}
Returns the chosen route from the strategy.
${<
feedbackList
>} 
Returns feedback information for the routing.
Even though both the ${<
route
>} and ${<
feedbackList
>.<
index
>.
route
} variables return the selected route from the strategy, they serve different purposes. The <
feedbackList
> variable may be referenced outside the loop and stored elsewhere externally, while the <
route
> variable is set each time the Execute Routing Strategy assertion is run. The <
feedback
> variable serves as an audit that can be analyzed later for decision-making purposes on routes.
Using the Assertion
  1. Do one of the following:
    • To add the assertion to the Policy Development window, see Add an Assertion.
    • To change the configuration of an existing assertion, proceed to step 2 below.
  2. Right-click "
    Execute Routing Strategy...
    " in the policy window and then select
    Execute Routing Strategy Properties
     or double-click the assertion in the policy window. The assertion properties are displayed. 
  3. Configure the properties as follows.
    Setting
    Description
    Routing Strategy Prefix
    Specify the context variable that is storing the chosen routing strategy. This should match the “Routing Strategy Prefix” entered in the
    Create Routing Strategy
     assertion.
    Default:
    strategy
    Route Variable Name
    Specify the context variable that will store the chosen route from the strategy.
    Default:
    route
    The default results in the variable ${
    route
    } that can be used to retrieve the route destination. This variable is set only for outbound messages.
    Feedback List
    Specify the context variable that will store the feedback from the routing. This feedback includes the Current Route information for both successful or failed routing attempts.
    Feedback is collected after each routing attempt and added to the Feedback List context variable only when the
    Process Routing Strategy Result
     assertion is run.
    Default:
    feedback
    The default results in the multivalued variable ${
    feedback
    }. This variable is set by both inbound and outbound messages
  4. Click [
    OK
    ]  when done.

Content feedback and comments