An association between a service access point (SAP) and how it is implemented.
The following syntax is simplified from Managed Object Format (MOF) code and includes all of the inherited properties.
Syntax
[Association, UMLPackagePath("CIM::Core::Device"), Version("2.10.0"), AMENDMENT]
class CIM_DeviceSAPImplementation : CIM_Dependency
{
CIM_LogicalDevice REF Antecedent;
CIM_ServiceAccessPoint REF Dependent;
};
Members
The CIM_DeviceSAPImplementation class has these types of members:
Properties
The CIM_DeviceSAPImplementation class has these properties.
Antecedent
Data type: CIM_LogicalDevice
Access type: Read-only
Qualifiers: key, Override ("Antecedent")
A CIM_LogicalDevice describing the logical device.
Dependent
Data type: CIM_ServiceAccessPoint
Access type: Read-only
Qualifiers: key, Override ("Dependent")
A CIM_ServiceAccessPoint describing the service access point implemented using the logical device.
Remarks
The cardinality of this association is many-to-many. A SAP can be provided by more than one logical device, operating in conjunction. And, any Device can provide more than one SAP. When many logical devices are associated with a single SAP, it is assumed that these elements operate in conjunction to provide the access point. If different implementations of a SAP exist, each of these implementations would result in individual instantiations of the service access point object. These individual instantiations would then have associations to the unique implementations.
Requirements
| Requirement | Value |
|---|---|
| Minimum supported client | Windows 8 |
| Minimum supported server | Windows Server 2012 |
| Namespace | Root\standardcimv2 |
| MOF | NetTCPIP.mof |
| DLL | NetTCPIP.dll |
See also
Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors (upstream author metadata: windowssdkdev). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
