Web-Based Enterprise Management
Web Based Enterprise Management (WBEM) is
systems management architecture initiative to unify the management of enterprise computing environments. WBEM allows the industry to deliver a set of standard-based management tools related to
XML.
The architecture has been standardised by the Distributed Management Task Force (previously the Desktop Management Task Force) â€" the
DMTF. They have developed a core set of standards that make up WBEM, which includes a data model, the
Common Information Model (CIM) standard.
The architecture is independent of the device being managed and has been applied to devices as diverse as IP Routers, Electrical Power Distribution Systems, Private Branch Exchanges (PBXs), Desktop Computers, Printers, and Storage Servers.
SMI-S is based on WBEM standard.
To understand the WBEM architecture, consider the components which lie between the operator trying to manage a device (configure it, turn it off and on, collect alarms, etc.) and the actual hardware and software of the device:
# the operator will presumably be presented with some form of graphical user interface (GUI), browser user interface (BUI), or command-line interface (CLI). The WBEM standard really has nothing to say about this interface (although a CLI for specific applications is being defined): in fact it is one of the strengths of WBEM that it is independent of the human interface since human interfaces can be changed without the rest of the system needing to be aware of the changes.# the GUI, BUI or CLI will interface with a WBEM client through a small set of Application Program Interfaces. This client will find the WBEM Server for the device being managed (typically on the device itself) and construct an XML message with the request.# the client will use the HTTP (or HTTPS) protocol to pass the request, encoding in CIM-XML, to the WBEM client# the WBEM server will decode the incoming request, perform the necessary authentication and authorisation checks and then consult the previously-created model of the device being managed to see how the request should be handled. This model is what makes the architecture so powerful: it represents the pivot point of the transaction with the client simply interacting with the model and the model interacting with the real hardware or software. The model is written using the Common Information Model standard and the
DMTF has published many models for commonly-managed devices and services: IP routers, Storage Servers, Desktop Computers, etc.# for most operations, the WBEM server determines from the model that it needs to communicate with the actual hardware or software. This is handled by so-called "providers": small pieces of code which interface between the WBEM server (using a standardised interface known as CMPI) and the real hardware or software. Because the interface is well-defined and the number of types of call is small, it is normally easy to write providers. In particular, the provider writer knows nothing of the GUI, BUI, or CLI being used by the operator.
So, which pieces of this does a device manufacturer or service provider have to write?
* Firstly the model.:This is normally done by extending as necessary one of the standard models published by the
DMTF.
* Then the BUI, GUI, or CLI. :The client and server usually do not need to be written because there are many open-source and commercial implementations available (see
#External links below)
* Then the providers:In summary, the WBEM architecture allows the manufacturer of a device or developer of a service to provide a standards-compliant management interface to that device simply and cheaply.
While using the HTTPS WBEM connection, it is important to verify unknown WBEM certificates before accepting them as valid certificates. Accepting an attacker owned certificate as a valid certificate discloses any transmitted password.
In a number of WBEM implementations, the providers run with elevated privileges. Unknown providers should not be loaded onto a system.
Standards
*Official WBEM page at DMTF, including standards documentsImplementations
*OpenPegasus â€" open-source client and server written in C++
*OpenWBEM â€" open-source client and server written in C++
*Windows Management Instrumentation â€" Microsoft's implementation for Windows
*Purgos â€" open-source management client for windows written C++
*PyWBEM - open-source WBEM library written in Python
