3.2.1 Abstract Data Model
This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with what is described in this document.
Note The abstract interface notation (Public) indicates that the Abstract Data Model element can be directly accessed from outside this protocol.
An MSDTC Connection Manager: OleTx Transports Protocol implementation MUST have two partners, as described in section 1.3.1. Within a session, based upon the comparison of their contact identifiers (CIDs): one partner is the primary partner, and the other is the secondary partner. For the sake of clarity, the term "local partner" is used to indicate the role that is being described, and the term "remote partner" is used to indicate the partner with which the local partner is communicating.
The abstract data model described in this section applies to an implementation of the MSDTC Connection Manager: OleTx Transports Protocol as a whole. Therefore, the IXnRemote server and IXnRemote client roles, which are both implemented by the local partner, share one instance of the model described here.
The MSDTC Connection Manager: OleTx Transports Protocol uses the registry to retrieve the values for the Server TCP Port and Service Network Protocols data elements described in this section, and the persistent store is shared with the MSDTC Connection Manager: OleTx Transaction Protocol [MS-DTCO] and the MSDTC Connection Manager: OleTx Management Protocol [MS-CMOM].