CHAPTER 3
EVENT MONITORING
ADU Event Monitoring
This chapter describes the events that are sent by the ADU Server. This chapter also explains how to assign a request on behalf of a client and how to establish monitoring criteria. The ADU Server continuously monitors the contents of ADUs for changes, and reports those changes to interested clients through event messages.
Clients register their interest in ADUs by assigning to the ADU Server with a monitoring criteria, which is a specification describing the condition that should generate an event notice. For example, a client might request notification when an agent enters wrapup state, or when an ADU is terminated. The client receives event messages about ADUs that match the specification, and continues to receive all events generated for those ADUs for as long as they match the client's monitoring criteria.
The ADU Server generates seven types of events that describe changes to existing ADUs. The following table lists the events and the contents of the event messages written in the ADU and sent to monitoring clients.
Event | Description | Message |
|
|
|
ADU.change | A modification has occurred in a monitored | All affected {name, value} |
| ADU. | couples and the ADUID. |
|
|
|
ADU.delete | Values have been deleted from the ADU. | All deleted values. |
|
|
|
ADU.drop | The ADU has changed and no longer | The ADUID. |
| matches the assign criteria. It will no |
|
| longer be monitored. If the ADU later |
|
| changes so that it again meets the assign |
|
| criteria, the client gets an ADU.watch |
|
| event. |
|
|
|
|
|
| (Sheet 1 of 2) |
|
|
|
27
