5.2 White Box Relationships
The following diagram illustrates the roles that the system takes when communicating with external entities by using the system member protocols listed in section 2.2.
Figure 20: Internal System Roles
The Core Transaction Manager Facet is the central piece of the system. It maintains a comprehensive data model to track the current list of transactions, transaction states, security settings, enlistment information, and system configuration data as described in [MS-DTCO] section 3.2.1.
The Core Transaction Manager Facet reads the registry keys and values generated by the Management Client to populate the data model for System Configuration.
All other roles and facets implemented by the system use the data model maintained by the Core Transaction Manager Facet to store shared state where needed, as described in section 5.1.1.
Management Server role uses the transaction list data available in the Core Transaction Manager Facet data model to build the transaction statistics when needed.
TIP Interoperability Provider Role establishes itself as a protocol extension with the Core Transaction Manager Facet by using the mechanism described in [MS-DTCO] section 3.2.1.5. Specific scenarios on how the TIP Interoperability Provider Role interacts with the Core Transaction Manager Facet are described in [MS-DTCM] section 1.3.
TIP Subordinate Transaction Manager Facet, TIP Superior Transaction Manager Facet, and TIP Transaction Manager Communicating with Application Facet are used for associating system internal transactions with TIP Transactions as described in [MS-TIPP]. The protocol described in [MS-TIPP] establishes itself as a protocol extension with the Core Transaction Manager Facet, by using the mechanism described in [MS-DTCO] section 3.2.1.5.
XA Superior Transaction Manager Facet and XA Resource Manager Bridge Facet as described in [MC-DTCXA] are used by the system to enable applications participate in transactions coordinated by XA Transaction Managers, and enable XA Resource Managers to participate in transactions coordinated by the system. Specific interactions between these facets and the Core Transaction Manager Facet are described in [MC-DTCXA] section 1.3.
Transaction Manager Communicating with an LU 6.2 Implementation Facet establishes itself as a protocol extension to the Core Transaction Manager Facet by using the mechanism described in [MS-DTCO] section 3.2.1.5. Specific scenarios how this Facet interacts with the Core Transaction Manager Facet are described in [MS-DTCLU] section 1.3. Section 3.3.1 in [MS-DTCLU] describes which abstract data model elements map to that of the Core Transaction Manager abstract data model.
Requesting Service Role, Activation Service Role, and Registration Service Role as described in [WSC10] and [WSC11] interact with the Core Transaction Manager Facet for transaction propagation and Two-Phase Commit protocol notifications. Participant Role and Coordinator Role as described in [WSAT10] and [WSAT11] interact with the Core Transaction Manager Facet for creating and completing transactions.
When interacting with protocols that depend on [MS-CMP], the system maintains the Common Details abstract data model specified in [MS-CMP] section 3.1.1. This data model maps to the IXnRemote Server and IXnRemote Client roles described in [MS-CMPO]. Details of how the data models described in [MS-CMP] interact with IXnRemote Server and IXnRemote Client are described in [MS-CMP] section 3.1.
