Neoview Workload Management Services Guide (R2.4)

Connection Rules
Connection rules determine which service to assign to the client session. Because connection
rules are the mechanism for assigning queries to services, you must create connection rules and
associate them with services if you plan to use the services that you created to manage query
workloads.
This section covers:
“How the NDCS Server Evaluates Connection Rules” (page 40)
Adding a Connection Rule” (page 42)
“Displaying the Definition of a Connection Rule” (page 44)
“Displaying the Definitions of All Connection Rules” (page 45)
Altering a Connection Rule” (page 46)
“Deleting a Connection Rule” (page 46)
Associating a Connection Rule With a Service” (page 47)
“Displaying the Connection Rules Associated With Services” (page 49)
“Displaying the Service Associated With a Connection Rule” (page 50)
How the NDCS Server Evaluates Connection Rules
When a client application connects to an NDCS server, the NDCS server retrieves the connection
rules from WMS and compares them with the client's connection attributes, set in ODBC, JDBC,
or .NET, to determine which service to assign to the client session.
The connection rules determine the service to assign to the client session based on one or more
of these connection attributes:
Session name (SESSION)
Application name (APPL)
Client login role (LOGIN)
Data source name (DSN)
The NDCS server evaluates each connection rule in the order in which you have associated the
connection rules with services. The NDCS server evaluates the first connection rule in the series
by comparing the connection attributes of the client session with the connection attribute
expressions defined in the connection rule. The connection attributes of the client session must
match all the connection attribute expressions defined in the connection rule for the NDCS server
to consider the connection rule to be true. If any of the connection attributes of the client session
do not match the connection attribute expressions defined in the connection rule, the NDCS
server considers the connection rule to be false and checks the next connection rule in the series.
For an example, see Figure 4-1 (page 41).
40 Configuring Rules