2.5.2.6 Delete CIM Object — WM Client

Goal: To use the WM client to delete an existing CIM object in the CIM repository.

Context of Use: This use case typically occurs when a WM user wants to remove a previously created object, such as an environment variable.

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 delete the object.

Preconditions

  • A CIM object already exists with the same class name as the CIM object that is to be deleted. When a CIM object is deleted, a CIM object is required to already exist with the same class name and unique identifier of the object that is to be deleted.

Main success scenario

  1. Trigger: The WM client sends a request to the server by specifying the class to be deleted. When deleting a CIM object, the WM client sends the class name and unique identifier of the object that is to be deleted.

  2. The WM server deletes the CIM object that the client identified.

  3. The WM server notifies the client that the object was deleted successfully.

Post condition

The specified object is deleted successfully.

Extensions: If the communication channel cannot be established, or it becomes disconnected, it causes the protocol to tear down all related communications and update any necessary data structures to maintain the system state, as described in section 2.10.1.