2.5.2.2 Invoke a Method on a CIM Object — WM Client
Goal: To invoke a method on a managed object.
Context of use: This use case typically occurs when a WM user wants to take an action on a managed object that the CIM methods on that object support.
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 invoke a method on the CIM object.
Preconditions
The WM user has to have a reference to a specific CIM object or class.
The WM user has to know the name of the method to be called and the name and type of the method parameters.
Main success scenario
Trigger: The WM client sends a request to the server by specifying the name and class of the CIM object to be accessed and the name of the method along with any required method input parameters to be executed on that object.
The WM server verifies that the targeted CIM object implements the specified method.
The WM server executes the method.
The WM server notifies the client that the method was invoked successfully.
Post condition
The method was executed successfully, and the results are returned to the WM user.
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. If the WM user refers to a nonexistent CIM object, the WM server notifies the WM client about the failure to perform the requested operation.