3.8.1 Abstract Data Model

  • Article

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 that described in this document.

Note that the abstract data model can be implemented in a variety of ways. This protocol does not prescribe or advocate any specific implementation technique.

The Subordinate Transaction Manager Facet (section 3.8) MUST maintain all the data elements as specified in section 3.1.1 and section 3.2.1.

Enlistment objects that are created by the subordinate transaction manager MUST provide the following properties as specified in section 3.1.1:

  • Name: The Name object referenced by the Name field of the Session object containing the connection object referenced by the Enlistment Object.Connection field of the Enlistment object

  • Enlistment Object.Identifier: An empty string

The subordinate transaction manager MUST provide the states as specified in the following sections for its supported connection types. Section 2.2.1.1.2 defines the connection types that a subordinate transaction manager MUST provide for each supported protocol version.