Avaya DXX-1015-01 manual Setting Event Monitoring Criteria, Monitoring Criteria Syntax

Setting Event Monitoring Criteria

Assigning to the ADU Server and monitoring an ADU do not add a client's name to the internal list of ADU-modifying clients. (The internal list of clients is described in “ADU Termination,” on page 12.) Assigning allows the client to watch the activity of an ADU. The client does not have to issue an ADU.Terminate() for each ADU being watched.

By default, a client's assign criteria is distributed to all ADU servers. If this is not desired, prefix the Assign or Monitor expression with a colon symbol (:):

For example:

[ADU.Assign(":loginid=wynn")]

If you specify both : and +, : must come first. So ":a=b" watches field a for value b, and reports only on those local vdus.

Note: In this sense, local means "this VDU server". If you fail over to a different VDU server, you may not get the result you were expecting.

iver=148

To test, try: [ADU.Assign(":state#Z")]

In a WAN, your ADU server should show events coming back for all logged in agents, but the other ADU servers should only get RemoteWatcher requests with empty strings, and should send no events back.

Setting Event Monitoring Criteria

ADUs are selected for monitoring by criteria matching. A criteria is an expression that selects some ADUs and rejects others according to a defined specification. If a criteria expression is provided as a parameter to the Assign() or Monitor() method, each name/value pair in the ADU is tested against it. If the criteria determine that a match exists, the ADU is watched. Subsequent changes are sent to the client as change events.

The following values cannot be successfully used in an Assign criteria:

createtime

createtimet

duration

endtime

suspend

￿termination transfercount.

Monitoring Criteria: Syntax

The general syntax of a criteria statement is:

method (name relationalop value [booleanop] name relationalop value)

Issue 1.0 June 2002 29