HP WBEM Services for HP-UX and Linux System Administrator's Guide

How Does HP WBEM Services Work?
How HP WBEM Services Processes Requests
Chapter 2 19
How HP WBEM Services Processes Requests
The client request is a CIM operation sent by HTTP to HP WBEM
Services. The request is encoded in XML (eXtensible Markup Language).
HP WBEM Service’s HTTP server listens for CIM messages on the
wbem-http or the wbem-https port.
1. First, the client connects to HP WBEM Services’ HTTP server. A
remote client sends a valid system login (name and password) to a
system with HP WBEM Services that has the appropriate provider
installed. For information about login permissions, see Chapter 6,
Security Considerations.
2. HP WBEM Services CIM Server uses its XML decoder to parse the
XML in the request. If there is an error, it returns an error message
and stops processing the request. Only a valid CIM operation is
accepted. A request could be rejected by the HTTP Server if it had
badly formed HTTP headers or badly formed XML.
For information about XML coding for CIM, see
http://dmtf.org/standards/WBEM.
3. If the request is valid, the CIM Server consults the CIM repository
and checks the following things:
• Does this namespace exist? If not, an error is returned and HP
WBEM Services stops processing the request. For example, the
osinfo request used in Chapter 4 has this namespace
information:
<LOCALNAMESPACEPATH>
<NAMESPACE NAME =”root”/>
<NAMESPACE NAME=”cimv2”/>
</LOCALNAMESPACEPATH>
• Does this user have permission in this namespace? If the HP
WBEM Services property enableNamespaceAuthorization is
set to true, HP WBEM Services will also check to be sure the user
is allowed access to this namespace. (See Chapter 6, Security
Considerations, for more about authorization.)
• Does this class exist? HP WBEM Services looks up the classname
given in the request.