Routing rules direct incoming client connections to the appropriate logical cluster. Once a connection is routed to a logical cluster, an Adaptive Server task entered for that route can be administered by logical cluster management capabilities.
There are three types of routing rules, or bindings. Each binding uses the name in the TDS login record.
Binding routes are listed in the order of precedence, from highest to lowest. Thus, a login route takes precedence over an application route, which takes precedence over an alias route.
Login routes – establish a relationship between an Adaptive Server login and a logical cluster.
Application routes – establish a relationship between an application name and a logical cluster.
Alias routes – associate a server name with a logical cluster. Applications can choose a logical cluster from server aliases placed in the interfaces file. These aliases use unique server names. The alias entry can point anywhere in the physical cluster. The workload manager sends it to the correct instances via login redirection.
