Information Technology - Architecture for Managed Computing Systems
|Publication Date:||30 December 2013|
Common Information Model (CIM) Infrastructure
The DMTF Common Information Model (CIM) Infrastructure is an approach to the management of systems and networks that applies the basic structuring and conceptualization techniques of the object-oriented paradigm. The approach uses a uniform modeling formalism that together with the basic repertoire of object-oriented constructs supports the cooperative development of an object-oriented schema across multiple organizations.
Clause 5 describes an object-oriented meta model based on the Unified Modeling Language (UML). This model includes expressions for common elements that must be clearly presented to management applications (for example, object classes, properties, methods, and associations).
Clause 5 does not describe specific CIM implementations, application programming interfaces (APIs), or communication protocols.
CIM Query Language Specification
The DMTF Common Information Model (CIM) uses a basic object-oriented structure and conceptualization techniques in its approach to managing hardware, software, systems, and networks. This approach provides a formal consistent model that enables cooperative development of an objectoriented schema across multiple organizations and problem domains.
Clause 6 describes a query language used to extract data from a CIM-based management infrastructure.
UML Profile for CIM
Clause 7 defines a UML profile which expresses the DMTF Common Information Model (CIM) using the OMG Unified Modeling Language (UML).
The specified mapping allows automated conversion between the DMTF defined CIM MOF file format or other equivalent representations of a CIM model and a UML model. This conversion can be done in both directions without loss of information, supporting round-trip engineering.
The mapping also allows creation of an XMI based representation of the UML Profile for CIM, for usage by UML tools. The UML Superstructure Specification and the OMG MOF/XMI Mapping Specification together define an XMI based file format for UML profiles.
Clause 7 is based on the CIM metamodel defined in the CIM Infrastructure described in clause 5. This document supports any CIM schema versions based upon that CIM metamodel.
Clause 7 uses the UML metamodel defined in the UML Superstructure Specification, Version 2.1.1.
WBEM is a set of DMTF standards that define how CIM modeled resources can be discovered, accessed and manipulated. DMTF defines a number of WBEM protocols for this purpose:
• CIM-XML: The protocol defined in the CIM Operations over HTTP Specification DSP0200, the Representation of CIM in XML Specification DSP0201 and the DTD for Representation of CIM in XML DSP0203.
• CIM-WS: The usage of the WS-Management protocol for CIM, as defined in the WS-Management CIM Binding Specification DSP0227, the WS-CIM Mapping Specification DSP0230, the Web Services for Management Specification DSP0226, and other underlying Web Services specifications.
• SM-CLP: The protocol defined in the Server Management Command Line Protocol Specification DSP0214, covering the core of the protocol common for all management profiles, and SM-CLP mapping specifications for each management profile, covering profile-specific aspects of the protocol such as verbs for extrinsic methods.
As different as these protocols are, they have certain operations and semantics in common, at least when looking at it from a higher level. These common semantics can be used to define generic operations. Clause 8 defines the model and behavior associated to these operations at a generic level, and common across the WBEM protocols.
The generic operations are expected to be used in the following areas:
• Future releases of CIM management profile specifications can define the support for intrinsic operations by referencing generic operations. Currently, they do that by referencing the operations defined for the CIM-XML protocol. Using generic operations allows the management profile specifications to become independent of protocols.
• Future and existing WBEM protocols can define their operations conformant to the generic operations. This drives more commonality across these protocols, and consequently makes it easier to support multiple protocols in client applications, server side instrumentation, and mapping bridges between protocols.
• Client APIs, server APIs and provider APIs can define their API calls conformant to the generic operations. This drives more commonality across these APIs and between these APIs and WBEM protocols, and consequently makes it easier to support multiple protocols with the same API in client libraries and server side instrumentation (e.g., provider APIs).
Management Profile Specification Usage Guide
Clause 9 defines the usage of and requirements for management profiles and management profile specification documents.
A management profile (short: profile) defines a management interface between implementations of a WBEM server and a WBEM client. In addition, a profile may define a management interface between a WBEM server and a WBEM listener for the delivery of indications. The management interfaces establish a contract between the involved WBEM components but are not an API because they do not define a programming interface. A profile defines a model and its behavior in the context of a management domain. Model and behavior are defined by selecting, specializing, and sometimes constraining elements from a schema and the set of operations (including indication delivery operations) for a particular purpose. A profile establishes a relationship between the model and the management domain. A profile defines use cases on the model that illustrate client visible behavior.
A management profile specification document (short: profile specification) contains the textual specification of one or more management profiles and may also contain content that does not specify a profile.
Profiles and profile specifications may be owned by DMTF or by other organizations.
The target audience for clause 9is anyone creating profiles or profile specifications (regardless of whether these are published by DMTF or published by other organizations), and implementers of profiles.
NOTE 1 Clause 9is not a template for a profile specification. To create a profile specification, start with the publishing organization's template and add clauses as described in clause 9. For profiles published by DMTF, use DSP1000.
NOTE 2 Clause 9 is not a profile specification; it defines the requirements for creating profiles or profile specifications.
Message Registry XML Schema Specification
ANNEX T provides an XML schema that defines the structure of DMTF message registries. A message registry is an XML instance document following this XML schema. A message registry defines messages that can be used to return errors using embedded instances of CIM_Error and indications based on CIM_AlertIndication.