CIM211 Class Declaration
CIM_AccountOnSystem

Table of Contents:
Class Hierarchy
Class Attributes
Class Qualifiers
Properties
Methods
Associations in which the class can participate
Sub Profiling Summary

Class Hierarchy

CIM_AccountOnSystem --> CIM_SystemComponent --> CIM_Component --> [top]

Class Attributes

Class Declaration Attributes
NameValue
SUPERCLASSCIM_SystemComponent
NAMECIM_AccountOnSystem

Class Qualifiers

Class CIM_AccountOnSystem Qualifiers
NameTypeValueFrom Class
Versionstring2.6.0 CIM_AccountOnSystem
DescriptionstringA system (e.g., ApplicationSystem, ComputerSystem, AdminDomain) aggregates Accounts and scopes the uniqueness of the Account names (i.e., userids). CIM_AccountOnSystem
Associationbooleantrue CIM_AccountOnSystem
Aggregationbooleantrue CIM_AccountOnSystem
DescriptionstringCIM_SystemComponent is a specialization of the CIM_Component association that establishes ’ part of ’ relationships between a System and any ManagedSystemElements of which it is composed. Use this association with caution when using it instead of a subclass such as SystemDevice or a peer association such as HostedService. This class is very broadly defined, which can lead to erroneous use. For example, Access Points that are dependent on (and hosted on) a System are NOT Components of the System. The System is not made up of any AccessPoint ’ parts ’ , which is why a Dependency association, HostedAccessPoint, was defined. Similarly, a PhysicalPackage is not a ’ part ’ of a System, because the physical element exists independently of any internal components, software, and so on. In fact, again, a Dependency relationship is true where a ComputerSystem is Dependent on its packaging, as described by the ComputerSystemPackage association. CIM_SystemComponent
Associationbooleantrue CIM_SystemComponent
Aggregationbooleantrue CIM_SystemComponent
Associationbooleantrue CIM_Component
Aggregationbooleantrue CIM_Component
DescriptionstringCIM_Component is a generic association used to establish ’ part of ’ relationships between Managed Elements. For example, it could be used to define the components or parts of a System. CIM_Component

Properties

Properties
NameTypeValueQualifiersClassOrigin
GroupComponentCIM_System ref Min
Max
Description
Override
Key
Aggregate
CIM_AccountOnSystem
PartComponentCIM_Account ref Weak
Description
Override
Key
CIM_AccountOnSystem

Property Qualifiers

Property GroupComponent Qualifiers
NameTypeValueFrom Class
Minuint321 CIM_AccountOnSystem
Maxuint321 CIM_AccountOnSystem
DescriptionstringThe aggregating system also provides name scoping for the Account. CIM_AccountOnSystem
OverridestringGroupComponent CIM_AccountOnSystem
Keybooleantrue CIM_AccountOnSystem
Aggregatebooleantrue CIM_AccountOnSystem

Property PartComponent Qualifiers
NameTypeValueFrom Class
Weakbooleantrue CIM_AccountOnSystem
DescriptionstringThe subordinate Account. CIM_AccountOnSystem
OverridestringPartComponent CIM_AccountOnSystem
Keybooleantrue CIM_AccountOnSystem

Property GroupComponent Qualifiers
NameTypeValueFrom Class
OverridestringGroupComponent CIM_SystemComponent
DescriptionstringThe parent System in the Association. CIM_SystemComponent
Keybooleantrue CIM_SystemComponent
Aggregatebooleantrue CIM_SystemComponent

Property PartComponent Qualifiers
NameTypeValueFrom Class
OverridestringPartComponent CIM_SystemComponent
DescriptionstringThe child element that is a component of a System. CIM_SystemComponent
Keybooleantrue CIM_SystemComponent

Property GroupComponent Qualifiers
NameTypeValueFrom Class
Keybooleantrue CIM_Component
Aggregatebooleantrue CIM_Component
DescriptionstringThe parent element in the association. CIM_Component

Property PartComponent Qualifiers
NameTypeValueFrom Class
Keybooleantrue CIM_Component
DescriptionstringThe child element in the association. CIM_Component

Methods

Method Qualifiers

Parameters

Parameter Qualifiers

Associations this class can participate in