1 krisbash 1.1 // Copyright (c) 2005 DMTF. All rights reserved.
2 // <change cr="SysDevCR00711.001" type ="change">Update of
3 // descriptions based on Tech Edit review.</change>
4 // <change cr="ArchCR00066.004" type="add">Add UmlPackagePath
5 // qualifier values to CIM Schema.</change>
6 // <change cr="CIMCoreCR00902" type="add">Promoted OtherIdentifyingInfo
7 // and IdentifyingDescription from ComputerSystem to System.</change>
8 // ==================================================================
9 // CIM_System
10 // ==================================================================
11 [Abstract, Version ( "2.15.0" ),
12 UMLPackagePath ( "CIM::Core::CoreElements" ),
13 Description (
14 "CIM_System represents an entity made up of component parts "
15 "(defined by the SystemComponent relationship), that operates "
16 "as a \'functional whole\'. Systems are top-level objects in "
17 "the CIM hierarchy, requiring no scoping or weak relationships "
18 "in order to exist and have context. It should be reasonable to "
19 "uniquely name and manage a System at an enterprise level. For "
20 "example, a ComputerSystem is a kind of System that can be "
21 "uniquely named and independently managed in an enterprise. "
22 krisbash 1.1 "However, these qualities are not true for the power supply (or "
23 "the power supply sub-\'system\') within the computer. \n"
24 "\n"
25 "Although a System can be viewed as a Collection, this view is "
26 "not the correct model. A Collection is simply a \'bag\' that "
27 "\'holds\' its members. A System is a higher-level abstraction, "
28 "built out of its individual components. It is more than the "
29 "sum of its parts. Note that System is a subclass of "
30 "EnabledLogicalElement which allows the entire abstraction to "
31 "be functionally enabled or disabled at a higher level than "
32 "enabling or disabling its component parts." )]
33 class CIM_System : CIM_EnabledLogicalElement {
34
35 [Key, Description (
36 "CreationClassName indicates the name of the class or the "
37 "subclass used in the creation of an instance. When used "
38 "with the other key properties of this class, this "
39 "property allows all instances of this class and its "
40 "subclasses to be uniquely identified." ),
41 MaxLen ( 256 )]
42 string CreationClassName;
43 krisbash 1.1
44 [Key, Override ( "Name" ),
45 Description (
46 "The inherited Name serves as the key of a System "
47 "instance in an enterprise environment." ),
48 MaxLen ( 256 )]
49 string Name;
50
51 [Description (
52 "The System object and its derivatives are top-level "
53 "objects of CIM. They provide the scope for numerous "
54 "components. Having unique System keys is required. A "
55 "heuristic can be defined in individual System subclasses "
56 "to attempt to always generate the same System Name Key. "
57 "The NameFormat property identifies how the System name "
58 "was generated, using the heuristic of the subclass." ),
59 MaxLen ( 64 )]
60 string NameFormat;
61
62 [Write, Description (
63 "The name of the primary system owner. The system owner "
64 krisbash 1.1 "is the primary user of the system." ),
65 MaxLen ( 64 ),
66 MappingStrings { "MIF.DMTF|General Information|001.3" }]
67 string PrimaryOwnerName;
68
69 [Write, Description (
70 "A string that provides information on how the primary "
71 "system owner can be reached (for example, phone number, "
72 "e-mail address, and so on)." ),
73 MaxLen ( 256 ),
74 MappingStrings { "MIF.DMTF|General Information|001.4" }]
75 string PrimaryOwnerContact;
76
77 [Write, Description (
78 "An array (bag) of strings that specifies the "
79 "administrator -defined roles this System plays in the "
80 "managed environment. Examples might be \'Building 8 "
81 "print server\' or \'Boise user directories\'. A single "
82 "system may perform multiple roles. \n"
83 "Note that the instrumentation view of the \'roles\' of a "
84 "System is defined by instantiating a specific subclass "
85 krisbash 1.1 "of System, or by properties in a subclass, or both. For "
86 "example, the purpose of a ComputerSystem is defined "
87 "using the Dedicated and OtherDedicatedDescription "
88 "properties." )]
89 string Roles[];
90
91 [Description (
92 "OtherIdentifyingInfo captures additional data, beyond "
93 "System Name information, that could be used to identify "
94 "a ComputerSystem. One example would be to hold the Fibre "
95 "Channel World-Wide Name (WWN) of a node. Note that if "
96 "only the Fibre Channel name is available and is unique "
97 "(able to be used as the System key), then this property "
98 "would be NULL and the WWN would become the System key, "
99 "its data placed in the Name property." ),
100 ArrayType ( "Indexed" ),
101 MaxLen ( 256 ),
102 ModelCorrespondence { "CIM_System.IdentifyingDescriptions" }]
103 string OtherIdentifyingInfo[];
104
105 [Description (
106 krisbash 1.1 "An array of free-form strings providing explanations and "
107 "details behind the entries in the OtherIdentifying Info "
108 "array. Note, each entry of this array is related to the "
109 "entry in OtherIdentifyingInfo that is located at the "
110 "same index." ),
111 ArrayType ( "Indexed" ),
112 ModelCorrespondence { "CIM_System.OtherIdentifyingInfo" }]
113 string IdentifyingDescriptions[];
114
115
116 };
|