Avaya DXX-1015-01 用户手册
Chapter 2 The Agent Data Unit
12 Agent Data Unit Server Programmer’s Guide
Any application that wants to interact with an ADU has to request it by its unique identifier, the
ADUID. Upon request, the ADU Server passes the ADUID out to other processes, thus enabling
applications to request access to individual ADUs.
ADUID. Upon request, the ADU Server passes the ADUID out to other processes, thus enabling
applications to request access to individual ADUs.
The ADU Server also honors requests to watch for ADUs that contain certain values. If any ADU
matches the monitoring criteria, the ADU Server issues event messages (which contain the
ADUID) to “interested” clients. (Refer to
matches the monitoring criteria, the ADU Server issues event messages (which contain the
ADUID) to “interested” clients. (Refer to
Typically, clients want to receive event notifications about ADUs, examine ADU contents, and
modify ADU values. These activities are supported through method invocations. For example, a
client could invoke one of the Get methods (GetOneValue(), GetSomeValues(), and so on) to ask
the ADU Server to return values in an ADU. Chapter 7 of this manual describes the methods
supporting these activities.
modify ADU values. These activities are supported through method invocations. For example, a
client could invoke one of the Get methods (GetOneValue(), GetSomeValues(), and so on) to ask
the ADU Server to return values in an ADU. Chapter 7 of this manual describes the methods
supporting these activities.
ADU Termination
When an agent logs out of Avaya IC, the agent’s ADU should be closed.
Before an ADU can be closed, the ADU Server must first verify that all processes are done with it.
For each ADU, the ADU Server maintains an internal list of processes that have read, transferred,
or modified the ADU. Any process that invokes a method using the ADUID of the ADU is added
to the list. When a client invokes the method ADU.Terminate(), the client's name is removed from
the list. When the list is empty, the ADU can be terminated.
For each ADU, the ADU Server maintains an internal list of processes that have read, transferred,
or modified the ADU. Any process that invokes a method using the ADUID of the ADU is added
to the list. When a client invokes the method ADU.Terminate(), the client's name is removed from
the list. When the list is empty, the ADU can be terminated.
Note: In some configurations, it is possible for the agent to log out of the teleset without logging
out of Avaya IC. The ADU is not closed in this case.
out of Avaya IC. The ADU is not closed in this case.
Safeguards are built into the ADU Server to terminate “suspicious” ADUs, in other words, those
that appear to have been lost. Any ADU that has been idle for an extended period (thirty minutes,
by default) is automatically terminated. (The idle time can be changed with the Idle Time
configuration parameter, as described in
that appear to have been lost. Any ADU that has been idle for an extended period (thirty minutes,
by default) is automatically terminated. (The idle time can be changed with the Idle Time
configuration parameter, as described in
If the ADU Server goes down, all ADUs are closed. For Agent Status monitors to be accurate, all
users must log off and log back on again to create new ADUs.
users must log off and log back on again to create new ADUs.
Listing Active ADUs
You can view a list of active ADUs and the clients interested in them with the listadu utility.
To use this utility:
1 Copy
listadu.exe
from the Avaya IC5.x/bin directory to the directory in which the
vesp.imp
and
vespidl.pk
files are located, which is /etc by default.
2 From the system prompt, type
listadu -iinterface -uusername -ppassword
-i interface to use (often ADU or VDU, or an alias or uuid of such a server)