Introduction
Technology Overview
Common Information Model (CIM)
Web Based Enterprise Management (WBEM)
Management Profiles
Management Initiatives
DMTF
Glossary

 


DMTF Tutorial > CIM > CIM Schema > Common Models > Systems Model

CIM Schema - Systems Model

Overview | CIM Specification | CIM Schema | Extension Schema

Core Model | Common Models

The CIM System Common Models defines computer-system related abstractions. Many of the concepts related to computer system derive from the CIM_System abstraction in the Core Model. CIM_System describes the aggregation of 'parts' (or components) into a single manageable 'whole' (the system).

Important concepts related to a CIM_System are:

  • Systems act as aggregation entities.
  • Systems are not modeled as a collection. A system is more than the sum of its parts. Systems have status and they host services and access points.
  • Systems are top-level objects that are frequently used to scope their aggregated entities.

Besides the concept of the computer system itself, the System Model also addresses compute components and functionality, associated with most computer systems. These include concepts such as file systems and files, operating systems, jobs, processes and threads, and diagnostics. In addition, both general purpose and 'dedicated' systems can be described. There are no specific subclasses to describe system functionality (i.e. routing, storage, storage array, and etc). The functionality of these systems is described by the services that are hosted or are capable of being hosted. Otherwise, you end up with individual subclasses routing, storage, etc. It is conceivable that a single system could provide all of these. Therefore, the dedicated property should be used to describe the primary functionalities that the system supports.

Server Example:

When examining a typical server, we are likely to find the following logical elements:

  • Several installed operating systems, one running operating system which has jobs and processes
  • Local and remote file System that are composed of directories and files.
  • Logical devices such as a Monitor, Keyboard, Mouse, Hard Disk, Processor, Power Supply, Fan, and etc.
  • Services that are hosted on the server itself, such as spell checker or a diagnostic service.
  • Services that are available to the server via service access points, such as a print service.

In addition, the server has physical aspects such as:

  • The server is contained in chassis or multiple chassis which may be mounted in a rack
  • The server consists of cards and components (chips)
  • The server occupies space at a known location

In the CIM environment the server is modularized into its elements. These elements are then associated to the computer system.

  • The elements denoted in blue are defined in the System Common Models.
  • The high level concepts of the elements denoted in white are defined in the Core Model.
  • The specific subclasses of PhyscialElements (denoted in green) are defined in the Physical Common Models.
  • The specific subclasses of Logical Device (not shown) are defined in the Device Common Models.
  • The asset aspects of Software are defined as SoftwareIdentity in the Core Model. While the deployment aspects of applications are defined in the Application Common Models.
Applications Event Network Support
Database Interop Physical Systems
Devices Metrics Policy User

Copyright © 2002-2006 Distributed Management Task Force, Inc. and WBEM Solutions, Inc.
All rights reserved.