The CIM_SoftwareElement class is used to decompose a CIM_SoftwareFeature object into a set of individually manageable or deployable parts for a particular platform. A software element's platform is uniquely identified by its underlying hardware architecture and operating system (for example Sun Solaris on Sun Sparc or Windows NT on Intel). As such, to understand the details of how the functionality of a particular software feature is provided on a particular platform, the CIM_SoftwareElement objects referenced by CIM_SoftwareFeatureSoftwareElement associations are organized in disjoint sets based on the TargetOperatingSystem property. A CIM_SoftwareElement object captures the management details of a part or component in one of four states characterized by the SoftwareElementState property.
CIM_SoftwareElement - child subclasses in ROOT\cimv2
' The value of this property is the manufacturer's identifier for this software element. Often this will be a stock keeping unit (SKU) or a part number.'
'The value of this property identifies the language edition of this software element. The language codes defined in ISO 639 should be used. Where the software element represents multi-lingual or international version of a product, the string multilingual should be used.'
' The OtherTargetOS property records the manufacturer and operating system type for a software element when the TargetOperatingSystem property has a value of 1 ("Other"). Therefore, when the TargetOperatingSystem property has a value of "Other", the OtherTargetOS property must have a non-null value. For all other values of TargetOperatingSystem, the OtherTargetOS property is to be NULL. '
' This is an identifier for this software element and is designed to be used in conjunction with other keys to create a unique representation of this CIM_SoftwareElement'
' The SoftwareElementState is defined in this model to identify various states of a software elements life cycle. - A software element in the deployable state describes the details necessary to successful distribute it and the details (conditions and actions) required to create a software element in the installable state (i.e., the next state). - A software element in the installable state describes the details necessary to successfully install it and the details (conditions and actions required to create a software element in the executable state (i.e., the next state). - A software element in the executable state describes the details necessary to successfully start it and the details (conditions and actions required to create a software element in the running state (i.e., the next state). - A software element in the running state describes the details necessary to monitor and operate on a start element.'
'The TargetOperatingSystem property allows the provider to specify the operating system environment. The value of this property does not ensure binary executable. Two other pieces of information are needed. First, the version of the OS needs to be specified using the OS version check. The second piece of information is the architecture the OS runs on. The combination of these constructs allows the provider to clearly identify the level of OS required for a particular software element.'
'The InstallDate property is datetime value indicating when the object was installed. A lack of a value does not indicate that the object is not installed.'
'The Status property is a string indicating the current status of the object. Various operational and non-operational statuses can be defined. Operational statuses are "OK", "Degraded" and "Pred Fail". "Pred Fail" indicates that an element may be functioning properly but predicting a failure in the near future. An example is a SMART-enabled hard drive. Non-operational statuses can also be specified. These are "Error", "Starting", "Stopping" and "Service". The latter, "Service", could apply during mirror-resilvering of a disk, reload of a user permissions list, or other administrative work. Not all such work is on-line, yet the managed element is neither "OK" nor in one of the other states.'
' The CIM_SoftwareElement class is used to decompose a CIM_SoftwareFeature object into a set of individually manageable or deployable parts for a particular platform. A software element's platform is uniquely identified by its underlying hardware architecture and operating system (for example Sun Solaris on Sun Sparc or Windows NT on Intel). As such, to understand the details of how the functionality of a particular software feature is provided on a particular platform, the CIM_SoftwareElement objects referenced by CIM_SoftwareFeatureSoftwareElement associations are organized in disjoint sets based on the TargetOperatingSystem property. A CIM_SoftwareElement object captures the management details of a part or component in one of four states characterized by the SoftwareElementState property. '