SMI Tutorial > SMI-S 1.1.0 Overview > SMI-S 1.1.0 Requirements > CIM-XML

Back

CIM-XML

Next

CIM-XML is the protocol that is used by SMI-S 1.1.0 to exchange CIM and WBEM information between a Client and a WBEM Agent. CIM-XML uses xmlCIM as the payload and HTTP as the transport. Currently, both HTTP 1.0 and 1.1 are supported. SMI-S 1.1.0 chose CIM-XML because it required by WBEM. Moreover, HTTP is a widely supported protocol that is usable by almost all existing infrastructures and over the Internet.

Using HTTP, SMI-S 1.1.0 can leverage the existing HTTP security mechanisms. To establish the connection to a WBEM Agent, a Client can use Basic or Digest authentication. Basic authentication sends the credential information in clear text while Digest authentication sends the credential information as encrypted data. SMI-S 1.1.0 also requires that the Client and WBEM Agent exchange the HTTP payload as encrypted data using the Secure Sockets Layer (SSL).

Using HTTP, SMI-S 1.1.0 can leverage the existing HTTP mechanisms to define extension headers. A SMI-S 1.1.0 WBEM Agent is required to support the HTTP operations of POST and MPOST. The CIM Operations over HTTP Specification v1.2 defines specific extension headers for a Client request and a WBEM Agent response. Different extension header are defined for single versus multiple (i.e., batch) operations.

The example below shows several CIM-XML extension headers for a GetClass operation on the root/cimv2 namespace

M-POST /cimom HTTP/1.0

Content-Type: text/xml;charset=UTF-8

Accept: text/xml, application/xml

Man: http://www.dmtf.org/cim/mapping/http/v1.0;ns=48

48-CIMProtocolVersion: 1.0

48-CIMOperation: MethodCall

48-CIMMethod: GetClass

48-CIMObject: root%2Fcimv2

User-Agent: Java1.2.1

Host: edoc5-pc

Content-length: 445

<?xml version="1.0" encoding="UTF-8"?>


 

 

Back Next