The Realm-Based Routing Table tab allows you to define the routing entries and associated proxy policies within the realm-based routing table (RFC 3588, section 2.7). The realm-based routing table is used to define a route entry’s associated servers in which the message should be relayed, redirected, or proxied.
NOTE: Click Add to insert a row and configure the routing information and Remove to delete. |
ID |
A unique ID |
|||||||
Realm |
Allows you to specify the Realm in which the application resides. Used as a primary key in the routing table lookups. |
|||||||
Vendor ID |
An Application is identified by a Vendor ID and an App ID. Used as a secondary key field in routing table lookups. Indicates the DRA Node supported Proxy mode for Application.
|
|||||||
Application |
||||||||
App ID |
||||||||
Spec |
Spec column is populated automatically when you select a predefined Application and indicates the specification number associated with the Application. Spec is not available when you define Custom Application. |
|||||||
Action |
Allows you to define how a message is to be treated. Options: Redirect, Relay, Proxy
|
|||||||
Host Usage |
Available only when Action is Redirect. Select Host Usage from the list. |
|||||||
Max Cache |
Available only when Action is Redirect and the value is automatically populated and you may change as required. |
|||||||
Server ID List |
Allows you to define one or more servers that is associated with the route entry (to which the message is to be routed).
|
|||||||
Set |
|