Reference Guide

Table 85. SoftwareInstallationServiceCapabilities (continued)
Property Description
● 10 = Log
● 11 = SilentMode
● 12 = AdministrativeMode
● .. = DMTF Reserved
● 32768..65535 = Vendor Specific
SupportedTargetTypes
An array containing a list of SoftwareIdentity.TargetType properties that this service
'knows' how to install. TargetType is an application specific string which is invariant
across version or name changes of the SoftwareIdentity and so can be used by a
client to select Software Identities compatible with this service. If the service is
generic (for example an OS installer), this array will be empty.
SupportedURISchemes
This property lists the URI schemes supported by the SoftwareInstallationService.
Possible values are:
● 2 = data
● 3 = file
● 4 = ftp
● 5 = http
● 6 = https
● 7 = nfs
● 8 = tftp
●
.. = DMTF Reserved
● 0x8000..0xFFFF = Vendor Specific
DCIM_ConcreteCollection
Table 86. ConcreteCollection
Property Description
ElementName
A user-friendly name for the object. This property allows each instance to define a
user-friendly name in addition to its key properties, identity data, and description
information.
NOTE: The Name property of ManagedSystemElement is also defined as a user-
friendly name. But, it is often subclassed to be a Key. It is not reasonable that the
same property can convey both identity and a user-friendly name, without
inconsistencies. Where Name exists and is not a Key (such as for instances of
LogicalDevice), the same information can be present in both the Name and
ElementName properties.
InstanceID
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely
identifies an instance of this class. To ensure uniqueness within the NameSpace, the
value of InstanceID should be constructed using the following preferred algorithm:
<OrgID> : <LocalID>
Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> must
include a copyrighted, trademarked, or otherwise unique name that is owned by the
business entity that is creating or defining the InstanceID or that is a registered ID
assigned to the business entity by a recognized global authority. (This requirement is
similar to the <Schema Name>_<Class Name> structure of Schema class names.) In
addition, to ensure uniqueness, <OrgID> must not contain a colon (:). When using
this algorithm, the first colon to appear in InstanceID must appear between <OrgID>
and <LocalID> . <LocalID> is chosen by the business entity and should not be reused
to identify different underlying (real-world) elements. If the above preferred
algorithm is not used, the defining entity must assure that the resulting InstanceID is
Dell Command | Monitor 10.2.1 classes and properties 223