3.7.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 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 superior transaction manager facet MUST maintain all the data elements that are specified in sections 3.1.1 and 3.2.1.

The Superior Transaction Manager facet MUST also maintain the following data elements:

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

  • Name: The Hostname field in the Enlistment object's connection object

  • Enlistment Object.Identifier: An empty string

The superior transaction manager MUST provide the states that are defined in the following sections for its supported connection types. Version-Specific Aspects of Connection Types Relevant to a Transaction Manager (section 2.2.1.1.2) defines the connection types that a superior transaction manager MUST provide for each supported protocol version.