Neoview Workload Management Services Guide (R2.5)

1. A client application requests a connection to the Neoview platform and passes its connection
attributes to the NDCS server.
2. The NDCS server requests connection rules from WMS.
3. WMS sends the connection rules to the NDCS server.
4. The NDCS server compares the connection attributes of the client application with the
connection rules from WMS.
5. If the connection attributes of the client application match a connection rule of a service, the
NDCS server assigns the client application's session to the service and sends a connection
complete request to the application.
At this time, the NDCS server runs any SQL commands that are specified for the service (in
SQL_DEFAULTS) and next runs any SQL commands that are specified for the connection
rule (in SQL_CMD).
If query statistics aggregation is enabled for the connection rule, the NDCS server loads the
aggregation parameters from WMS and stores them in its global memory.
6. If the connection attributes of the client application do not match any of the connection rules,
the NDCS server assigns the client session to the default service, HP_DEFAULT_SERVICE,
and sends a connection complete request to the application.
Figure 1-2 (page 23) shows how the NDCS server assigns a client session to a service.
Figure 1-2 How the NDCS Server Assigns a Client Session to a Service
The NDCS server assigns the
client session to the service.
vst106.vsd
Yes
Do the connection
attributes match the
connection rule of a
service?
No
Incoming
client
session
The NDCS server assigns the client
session to HP_DEFAULT_SERVICE.
The NDCS server gets the
connection attributes
of the session.
WMS sets and
saves the warning
level to low.
Is WARN-LOW defined
for the connection
rule?
WMS sets and
saves the warning
level to low.
WMS does not set
or save the
warning level.
Yes
No
Are there user-defined
connection rules in
WMS?
Yes
No
How WMS Applies Rules and Services 23