MSISCSITARGET_DeviceSAPImplementation, ROOT\CIMV2\storage\iscsitarget

Class | Methods | Properties (2) | Qualifiers (5) | Instances | Namespaces (1)
Samples: VB Script | C# | VB.Net | Search on:Microsoft

Description

An association between a ServiceAccessPoint (SAP) and how it is implemented. The cardinality of this association is many-to-many. A SAP can be provided by more than one LogicalDevice, operating in conjunction. And, any Device can provide more than one ServiceAccessPoint. When many LogicalDevices are associated with a single SAP, it is assumed that these elements operate in conjunction to provide the AccessPoint. If different implementations of a SAP exist, each of these implementations would result in individual instantiations of the ServiceAccessPoint object. These individual instantiations would then have associations to the unique implementations.

MSISCSITARGET_DeviceSAPImplementation properties

MSISCSITARGET_DeviceSAPImplementation has 2 properties (2 Derived)

NameOriginCIMType
key
Antecedent
CIM_Dependency102 [ref:CIM_LogicalDevice]
key
Dependent
CIM_Dependency102 [ref:CIM_ServiceAccessPoint]

Detailed description of MSISCSITARGET_DeviceSAPImplementation properties

Derived properties (2) of MSISCSITARGET_DeviceSAPImplementation class

Antecedent property
CIMTYPE'ref:CIM_LogicalDevice'
keyTrue
Antecedent property is in 35 classes of ROOT\CIMV2\storage\iscsitarget and in 15 namespaces
Dependent property
CIMTYPE'ref:CIM_ServiceAccessPoint'
keyTrue
Dependent property is in 35 classes of ROOT\CIMV2\storage\iscsitarget and in 15 namespaces

MSISCSITARGET_DeviceSAPImplementation Qualifiers

NameValueToInstanceToSubclassOverridableAmendedLocal
AssociationTrue
Description'An association between a ServiceAccessPoint (SAP) and how it is implemented. The cardinality of this association is many-to-many. A SAP can be provided by more than one LogicalDevice, operating in conjunction. And, any Device can provide more than one ServiceAccessPoint. When many LogicalDevices are associated with a single SAP, it is assumed that these elements operate in conjunction to provide the AccessPoint. If different implementations of a SAP exist, each of these implementations would result in individual instantiations of the ServiceAccessPoint object. These individual instantiations would then have associations to the unique implementations.'
dynamicTrue
provider'MSiSCSITargetProv'
Version'1.0.0'

MSISCSITARGET_DeviceSAPImplementation System properties

NameValueOriginCIMTypeLocalArray
__PATH'\\.\ROOT\CIMV2\storage\iscsitarget:MSISCSITARGET_DeviceSAPImplementation'___SYSTEM8
__NAMESPACE'ROOT\CIMV2\storage\iscsitarget'___SYSTEM8
__SERVER'.'___SYSTEM8
__DERIVATION['CIM_DeviceSAPImplementation', 'CIM_Dependency']___SYSTEM8
__PROPERTY_COUNT2___SYSTEM3
__RELPATH'MSISCSITARGET_DeviceSAPImplementation'___SYSTEM8
__DYNASTY'CIM_Dependency'___SYSTEM8
__SUPERCLASS'CIM_DeviceSAPImplementation'___SYSTEM8
__CLASS'MSISCSITARGET_DeviceSAPImplementation'___SYSTEM8
__GENUS1___SYSTEM3

Similar Classes to MSISCSITARGET_DeviceSAPImplementation

Number of classes:2
Class nameChildsPropertiesMethodsClass
Instances
Child
Instances
AbstractSingleton
CIM_DeviceSAPImplementation220---
MSFTSMNET_DeviceSAPImplementation020----
comments powered by Disqus
WUtils.com