Example of Routing Rules | Teradata Unity - 17.00 - Example of Routing Rules - Continuous Availability - Teradata Unity

Teradata® Unity™ User Guide

Product
Continuous Availability
Teradata Unity
Release Number
17.00
Published
September 2020
Language
English (United States)
Last Update
2020-09-15
dita:mapPath
fmz1594836948704.ditamap
dita:ditavalPath
qqk1595871525984.ditaval

All sessions that successfully connect to Unity are mapped to a routing rule by evaluating the user mapping rules. The user mapping rules are specified by userid, region, account string, and role. The Routing Rule name refers to a specific rule that defines Read and Write request routing properties such as to which system to send the request if a Preferred routing is specified. Profiles refers to a specific error profile that defines whether to exit or failover when a specific error occurs.

Priority User ID Region Account String Role Profile Routing Rule
1 Susan RegionA * * * RoutingA
2 John * * DBA * RoutingA
3 * * * DBA * RoutingB
4 * * CRM * * RoutingC
5 * * * * * DefaultRouting

The first rule with Priority 1 says that if Susan logs on from RegionA, Unity performs session routing based on the rules defined in RoutingA. The wildcard in Profile means that all error profiles are used. If John logs on with an assigned DBA role, then Unity performs session routing also using the RoutingA rule. Otherwise, any user who logs on with the DBA role initiates a session that uses RoutingB.