Class CIM_CollectionOfMSEs
extends CIM_Collection

The CollectionOfMSEs object allows the grouping of ManagedSystemElements for various identification purposesand to reduce the complexity of associating Settings andConfigurations. It is abstract to require furtherdefinition and semantic refinement in subclasses. TheCollectionOfMSEs object does not carry any state or statusinformation, but only represents a grouping or 'bag' of Elements. Forthis reason, it is incorrect to subclass groups that havestate/status from CollectionOfMSEs - an example isCIM_RedundancyGroup (which is correctly subclassed fromLogicalElement). Collections typically aggregate 'like'objects, but are not required to do so. They simply identify 'bags' and may represent an optimization. This is especiallytrue with respect to their association to Settings andConfigurations. Without Collections, one is forcedto define individual ElementSetting andElementConfiguration associations, to tie Settings and Configurationobjects to individual ManagedSystemElements. There may be muchduplication in assigning the same Setting tomultiple objects. In addition, using the Collection object allows thedetermination that the Setting and Configurationassociations are indeed the same for the Collection's members.This information would otherwise be obtained by definingthe Collection in a proprietary manner, and thenquerying the ElementSetting and ElementConfigurationassociations to determine ifthe Collection set is completely covered.

Class Hierarchy

CIM_ManagedElement
   |
   +--CIM_Collection
   |
   +--CIM_CollectionOfMSEs

Direct Known Subclasses

CIM_DiskGroup
CIM_LogicalNetwork
CIM_IPSubnet
CIM_LANSegment
CIM_IPXNetwork
CIM_IPAddressRange
CIM_BGPCluster
CIM_BGPPeerGroup
CIM_BufferPool

Class Qualifiers

NameData TypeValueScopeFlavors
AbstractbooleantrueTOSUBCLASS= falseOVERRIDABLE= false
DescriptionstringThe CollectionOfMSEs object allows the grouping of ManagedSystemElements for various identification purposesand to reduce the complexity of associating Settings andConfigurations. It is abstract to require furtherdefinition and semantic refinement in subclasses. TheCollectionOfMSEs object does not carry any state or statusinformation, but only represents a grouping or 'bag' of Elements. Forthis reason, it is incorrect to subclass groups that havestate/status from CollectionOfMSEs - an example isCIM_RedundancyGroup (which is correctly subclassed fromLogicalElement). Collections typically aggregate 'like'objects, but are not required to do so. They simply identify 'bags' and may represent an optimization. This is especiallytrue with respect to their association to Settings andConfigurations. Without Collections, one is forcedto define individual ElementSetting andElementConfiguration associations, to tie Settings and Configurationobjects to individual ManagedSystemElements. There may be muchduplication in assigning the same Setting tomultiple objects. In addition, using the Collection object allows thedetermination that the Setting and Configurationassociations are indeed the same for the Collection's members.This information would otherwise be obtained by definingthe Collection in a proprietary manner, and thenquerying the ElementSetting and ElementConfigurationassociations to determine ifthe Collection set is completely covered.None TRANSLATABLE= true

Local Class Properties

NameData TypeQualifiers
NameData TypeValueScopeFlavors
CollectionIDstring
DescriptionstringThe identification of the Collection object. When subclassed, the CollectionID property can be overridden to be a Key property.None TRANSLATABLE= true
MaxLenuint32256None None

Inherited Properties

NameData TypeClass Origin
CaptionstringCIM_ManagedElement
DescriptionstringCIM_ManagedElement