ABSTRACT
Before talking about clients and their architectures and implementations, it is important to be clear that WBEM clients are not user interfaces. As we have seen before, the chain of components is as follows:
The WBEM client represents the operator in negotiations with the WBEM server; it converts the operator’s requests into CIM-XML from whatever language is natural for the operator and it translates the WBEM server’s response back. It is not responsible for producing drop-down menus on an operator’s workstation, rendering HTML onto a screen, or parsing the text of a command line interface; that is the function of the operator interface software. Of course, the operator interface and WBEM client may be (and often are) implemented in the same piece of code.
