1、American National StandardDeveloped byfor Information Technology CIM Representations for ManagementINCITS 498-2012INCITS 498-2012Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-
2、Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-INCITS 498-2012American National Standardfor Information Technology CIM Representationsfor ManagementSecretariatInformation Techn
3、ology Industry CouncilApproved October 16, 2012American National Standards Institute, Inc.Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval of an American National Standa
4、rd requires review by ANSI that therequirements for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially a
5、ffected interests. Substantial agreement means much more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objections be considered, and that a concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary; th
6、eirexistence does not in any respect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no
7、circumstances give an interpretation of any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secr
8、etariat or sponsor whose name appears on the titlepage of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this st
9、andard. Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2012 by I
10、nformation Technology Industry Council (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of ITI, 1101 K Street NW, Suite 610, Washington, DC 20005. Printed in the United States of America
11、CAUTION: The developers of this standard have requested that holders of patents that may berequired for the implementation of the standard disclose such patents to the publisher. However,neither the developers nor the publisher have undertaken a patent search in order to identifywhich, if any, paten
12、ts may apply to this standard. As of the date of publication of this standardand following calls for the identification of patents that may be required for the implementation ofthe standard, no such claims have been made. No further patent search is conducted by the de-veloper or publisher in respec
13、t to any standard it processes. No representation is made or impliedthat licenses are not required to avoid infringement in the use of this standard.Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without l
14、icense from IHS-,-,-i CONTENTS Foreword.vii Introduction . 1 Document conventions 1 Typographical conventions . 1 ABNF usage conventions . 2 Deprecated material 2 1 Scope 3 1.1 Representation of CIM in XML 3 1.2 WBEM URI Mapping . 3 1.3 SM CLP-to-CIM Common Mapping 3 1.4 WS-Management CIM Binding .
15、3 1.5 WS-CIM Mapping 3 2 Normative references 4 3 Terms and definitions 6 4 Symbols and abbreviated terms 7 5 Representation of CIM in XML 9 5.1 Overview . 9 5.1.1 CIM in XML 9 5.1.2 Rendering to MOF . 10 5.1.3 Mapping choices 10 5.2 Entity Descriptions 11 5.2.1 CIMName . 11 5.2.2 CIMType 11 5.2.3 Q
16、ualifierFlavor 11 5.2.4 ClassOrigin 11 5.2.5 Propagated 11 5.2.6 ArraySize . 12 5.2.7 SuperClass 12 5.2.8 ClassName 12 5.2.9 ReferenceClass . 12 5.2.10 ParamType 12 5.2.11 EmbeddedObject . 13 5.3 Element descriptions . 13 5.3.1 Top-level element: CIM 13 5.3.2 Declaration elements . 13 5.3.3 Value el
17、ements 15 5.3.4 Naming and location elements 18 5.3.5 Object definition elements . 21 5.3.6 Message elements . 25 6 WBEM URI Mapping . 30 6.1 General . 30 6.2 Namespace type or scheme . 31 6.3 Authority 31 6.4 Namespace name . 31 6.5 Model path encoding. 32 6.6 Collected BNF for WBEM URI 33 6.7 WBEM
18、 URI examples . 35 6.7.1 Untyped model path . 35 6.7.2 Typed model path 35 7 SM CLP-to-CIM Common Mapping 36 7.1 Overview . 36 Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ii
19、 7.1.1 General 36 7.1.2 Evaluating and applying an SM CLP command 36 7.1.3 SM CLP-to-CIM command mapping 36 7.1.4 Addressing requirements . 36 7.1.5 Determining requirements for supporting functionality 37 7.2 Conventions 37 7.2.1 Notation 37 7.2.2 Pseudo-code conventions . 37 7.3 SM CLP-to-CIM prop
20、erty mapping . 39 7.3.1 CIM MOF property data type-based value format . 39 7.3.2 SM CLP data type modifier-based value format 40 7.3.3 CLP-to-CIM property value string formats . 40 7.4 Common mapping components 42 7.4.1 Common mapping functions 42 7.4.2 SM CLP-to-CIM command mapping functions for co
21、mmon object classes 47 7.4.3 SM CLP-to-CIM command mapping functions for intrinsic operations 61 7.4.4 SM CLP-to-CIM common messages . 66 7.5 SM CLP-to-CIM common verb mappings . 67 7.5.1 cd . 67 7.5.2 exit . 68 7.5.3 help 68 7.5.4 version . 68 8 WS-Management CIM Binding 70 8.1 Prefixes and XML nam
22、espaces 70 8.2 WS-Management default addressing model 70 8.2.1 Class-Specific ResourceURI 71 8.2.2 “All Classes” ResourceURI 72 8.2.3 Accounting for different CIM namespaces . 73 8.3 Accessing instances . 73 8.3.1 Get . 74 8.3.2 Put 74 8.3.3 Delete . 74 8.3.4 Create 74 8.4 Filter dialects . 75 8.4.1
23、 CQL 75 8.4.2 Association queries 77 8.5 Enumeration 83 8.5.1 EnumerationMode 83 8.5.2 XmlFragment . 83 8.5.3 Polymorphism 84 8.5.4 XPath enumeration using the class-specific ResourceURI . 86 8.5.5 XPath enumerate using the “all classes” ResourceURI 87 8.6 Subscriptions 88 8.6.1 Indication filters 8
24、8 8.6.2 Subscribe request 89 8.6.3 Subscription response . 93 8.6.4 Event delivery 93 8.6.5 Subscription reporting 94 8.6.6 Unsubscribe and renew requests 97 8.7 Extrinsic methods 98 8.8 Exceptions 98 8.8.1 Fault responses to method errors 98 8.8.2 Advertisement of fault CIM_Error inclusion . 100 8.
25、9 CIM specific WS-Management options . 101 8.9.1 ShowExtensions option . 101 8.10 Instance representation 102 Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-iii 8.11 Client acc
26、ess to CIM class metadata 102 8.11.1 Applicability 102 8.11.2 Non-separability of metadata access functions . 102 8.11.3 Overview of metadata operations 102 8.11.4 Targets of metadata operations . 103 8.11.5 Class metadata 104 8.11.6 Target properties 104 8.11.7 Selectors 104 8.11.8 Options . 105 8.
27、11.9 EPR 107 8.11.10 Paths 107 8.11.11 Advertisement of CIM class metadata path types . 108 8.11.12 Examples of path EPR containing URL . 109 8.11.13 Example: Get CIM-XML class metadata for CIM_ComputerSystem . 110 8.11.14 Example: Enumerate EPRs for class metadata for CIM_ComputerSystem and classes
28、 derived from it . 112 8.11.15 Example: Enumerate WS-CIM class metadata for CIM_ComputerSystem and classes derived from it . 114 8.11.16 Example: Enumerate CIM-XML class metadata and EPRs for CIM_ComputerSystem and classes derived from it 116 8.12 Fault codes . 118 8.12.1 wsmb:CIMException 118 8.12.
29、2 wsmb:PolymorphismModeNotSupported 119 8.13 Mapping for DSP0200 CIM operations . 119 8.13.1 Supported operations 119 8.13.2 Unsupported operations 128 8.14 Mapping of error messages to SOAP fault subcodes . 129 8.15 XSD . 130 8.16 WSDL 130 9 WS-CIM Mapping 131 9.1 Namespace prefixes and schema loca
30、tions . 131 9.2 Dereferencing schema URI locations in order to access XML schema 132 9.2.1 General 132 9.2.2 Validation of CIM instances . 133 9.3 Mapping primitive datatypes . 133 9.3.1 cimDateTime Datatype 134 9.3.2 CIM references 135 9.3.3 cimAnySimpleType datatype . 136 9.3.4 Derivation by restr
31、iction . 137 9.3.5 WS-CIM canonical values 137 9.4 CIM Class to XML schema mappings . 137 9.4.1 Class namespace 137 9.4.2 Properties . 138 9.4.3 Class structure . 147 9.4.4 Class inheritance . 149 9.4.5 Method parameters 150 9.4.6 CIM instances 153 9.4.7 Superclass class representation 154 9.5 CIM m
32、ethods to WSDL mappings 155 9.5.1 Defining WSDL message structures 155 9.5.2 Defining WSDL operation structures . 156 9.5.3 Defining wsa:Actions . 156 9.6 Qualifier mappings 157 9.6.1 General format . 157 9.6.2 Mapping CIM qualifiers to XSD elements 159 9.6.3 Inheritance of qualifiers 162 Copyright
33、American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-iv Annex A (informative) Per-profile mappings 163 A.1 Preconditions and assumptions for per-profile SM CLP-to-CIM command mapping behaviors
34、 163 A.1.1 Preconditions . 163 A.1.2 Assumptions 163 Annex B (informative) Schemas 165 B.1 Common WS-CIM schema: DSP8004 165 B.2 Qualifiers schema: DSP8005 168 B.3 Class hierarchy type schema: DSP8006 170 Annex C (informative) Examples . 171 C.1 MOF definitions . 171 C.1.1 EX_BaseComponent . 171 C.1
35、.2 EX_DerivedComponent . 171 C.1.3 EX_AssociationComponent . 172 C.2 XSD . 172 C.2.1 EX_BaseComponent . 172 C.2.2 EX_DerivedComponent . 173 C.2.3 EX_AssociationComponent . 175 C.2.4 Class hierarchy schema 176 C.3 WSDL fragments . 176 C.4 MetaData fragments . 177 C.4.1 EX_BaseComponent . 177 C.4.2 EX
36、_DerivedComponent . 178 Annex D (informative) Collation optimization available to implementers . 181 D.1 Sorting with limited character set 181 D.2 Note of caution concerning collation . 181 Annex E (informative) Conformance for WS-Management CIM Binding . 183 Annex F (informative) Conformance for W
37、S-Management CIM Mapping 184 Annex G (informative) Bibliography . 185 Figures Figure 1 WBEM URI as a mapping of CIM object name to IETF URI . 31 Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without licen
38、se from IHS-,-,-v Tables Table 1 Component documents . 2 Table 2 ERROR data type fields . 38 Table 3 CommandStatus data type fields 38 Table 4 Message data type fields 39 Table 5 CLP-to-CIM property value string formats 40 Table 6 Common SM CLP Messages 66 Table 7 Prefixes and XML namespaces 70 Tabl
39、e 8 CIM_IndicationFilter properties . 95 Table 9 CIM_ListenerDestinationWSManagement required properties . 95 Table 10 CIM_ListenerDestinationWSManagement optional properties . 95 Table 11 CIM_IndicationSubscription and CIM_FilterCollectionSubscription required properties 96 Table 12 GenOps operatio
40、ns and WS-Management equivalents . 103 Table 13 Targets used in ResourceURI to enumerate or get class information 104 Table 14 Properties of a class ResourceURI . 104 Table 15 Options that may be included in operations targeted at metadata . 105 Table 16 Examples of the impact of option combinations
41、 on operations targeted at metadata 106 Table 17 Elements of the EPR of an operation targeted at metadata . 107 Table 18 wsmb:CIMException . 118 Table 19 wsmb:PolymorphismModeNotSupported . 119 Table 20 GetInstance . 120 Table 21 GetInstance arguments . 120 Table 22 GetInstance error codes . 120 Tab
42、le 23 DeleteInstance 120 Table 24 DeleteInstance arguments 121 Table 25 DeleteInstance error codes . 121 Table 26 ModifyInstance 121 Table 27 ModifyInstance arguments 121 Table 28 ModifyInstance error codes . 122 Table 29 CreateInstance 122 Table 30 CreateInstance arguments 122 Table 31 CreateInstan
43、ce error codes 122 Table 32 EnumerateInstances . 123 Table 33 EnumerateInstances arguments . 123 Table 34 EnumerateInstances error codes 123 Table 35 EnumerateInstanceNames . 124 Table 36 EnumerateInstanceNames arguments . 124 Table 37 EnumerateInstanceNames error codes 124 Table 38 Associators 125
44、Table 39 Associators arguments . 125 Table 40 Associators error codes 125 Table 41 AssociatorNames 126 Table 42 AssociatorNames arguments 126 Table 43 AssociatorNames error codes . 126 Table 44 References 127 Table 45 References arguments 127 Copyright American National Standards Institute Provided
45、by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-vi Table 46 References error codes 127 Table 47 ReferenceNames 128 Table 48 ReferenceNames arguments 128 Table 49 ReferenceNames error codes . 128 Table 50 CIM error messages with corres
46、ponding subcode mappings . 129 Table 51 Namespaces . 131 Table 52 Namespace prefixes . 131 Table 53 Schema URI locations 132 Table 54 XSD DSP numbers . 132 Table 55 Mapping CIM datatypes to WS-CIM datatypes . 133 Table 56 Rules for converting datetime to cimDateTime . 135 Table 57 Rules for converti
47、ng cimDateTime to datetime . 135 Table 58 CIM qualifiers mapped to XSD elements 160 Table 59 Rules of qualifier inheritance . 162 Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,
48、-viiForeword (This foreword is not part of American National Standard INCITS 498-2012.)CIM Representations for Management was prepared by the DMTF Server Manage-ment Working Group and the following working groups of the DMTF InfrastructureSubcommittee:- WEBM Infrastructure and Protocols Working Group- WBEM Modeling Working Group- WS-Management Working GroupDMTF is a not-for-profit association of industry members dedicated to promoting en-ter
