2.5.2.5 Monitor Events— WM Client

Goal: The goal is to submit a query to the WM server and to have the WM server notify the submitting user when conditions that are given in the query are met.

Context of Use: This use case occurs when the WM user wants to be alerted to specific changes in the monitored objects.

Actors

  • WM client: The primary actor that triggers this use case. It is responsible for providing an interface to the CIM data for some set of computers. The primary interest of the WM client is to provide such functionality.

  • WM server: A supporting actor who implements a CIMOM and responds to network requests that the WM client initiates.

  • Authentication services: A supporting actor that provides authentication services through NTLM, Kerberos, Basic, and Digest authentication to secure communications. It also provides authentication services that support the client-to-server communication. For an overview of the Authentication Services protocols, see [MS-AUTHSOD].

Stakeholders

  • WM user: A person who or a management application that has to access or change some set of CIM data for some set of computers. The primary interest of the WM user is to monitor the required events.

Preconditions

  • The WM user knows the type of events to which it wants to subscribe.

Main success scenario

  1. Trigger: The WM client sends the query to the server.

  2. The WM server then stores the query.

  3. If or when an event is generated that matches the query, the WM server delivers the event notifications to the client.

Post condition

The WM server delivers all requested notifications of events to the WM user.

Extensions: None.