|
DMTF Tutorial
> CIM > CIM
Schema > Core Model
 |
CIM Schema Core Model
|
 |
Overview | CIM Specification | CIM Schema | Extension Schema
Core Model
| Common Models
The core model establishes a basic classification of the classes and
associations of the managed environment. The class hierarchy begins with the
abstract Managed Element class which is in turn subclassed to Managed
System Element, the Product related classes, Setting and Configuration,
Collection and the Statistical Data classes, among others. From
the classes in the Core Model, the model expands in many directions,
addressing many management domains and relationships between managed
entities.
The Core Model is Broken Down into the Following Sections:
- Qualifiers
- Core Elements/Base Classes (e.g, ManagedElement, LogicalElement, System, Service, Dependency, Component, LogicalIdentity)
- PhysicalElements & Location
- SoftwareIdentity
- Devices
- StorageExtents (subclass of LogicalDevice)
- Collections
- Product and FRUs (Field Replaceable Unit)
- Statistics
- Capabilities
- Settings
- Power Management
Significant Classes and Associations of the Core Model:
The Managed Element class roots the CIM object hierarchy and acts
as a reference for associations that apply to all entities in the
hierarchy.
Managed System Elements represent Systems, components of Systems,
any kinds of services (functionality), software and networks. The
definition of "System" in the CIM context is quite broad,
ranging from computer systems and dedicated devices, to application
systems and network domains.
Both Logical and Physical Elements are subclasses of Managed System
Element. Further definition and specification of these subclasses
are provided in the Core and Common Models. For example, System
and Logical Device objects are subclasses of Logical Element, defined
in the Core Model.
Products represent contracts between vendors and consumers, and
capture information about how the Product was acquired, how it is
supported, and where it is installed.
Settings define specific, pre-configured parameter data to be "applied"
(loosely transitionally) to one or more Managed System Elements.
Their definition is very much tied to the properties of existing objects through the Element
Setting association. Configurations aggregate Settings and Dependencies,
representing a certain behavior or desired functional state for
Managed System Elements.
The Statistical Information class is the abstract super class
for any kind of statistical data related to a Managed Element. The Element
to which the Statistical Information applies is indicated via the
Statistics association.
Collections represent arbitrary "bags" that group Managed
Elements together. Membership can be described by the class definition
and/or indicated by explicit instantiation of the Member Of Collection
association.
Component associations establish 'part of' relationships
between Managed Elements.
Dependency associations describe functional dependencies (one
object cannot function independent of the other) or existence dependencies
(the object cannot exist independent of the other) between Managed Elements.
|
