3.2.1.4 Transaction Manager Facets

An OleTx transaction manager is subdivided into the following transaction manager facets:

• Core Transaction Manager Facet

• Transaction Manager Communicating with an Application Facet

• Transaction manager Communicating with a Resource Manager Facet

• Superior Transaction Manager Facet

• Subordinate Transaction Manager Facet

These facets MUST communicate with each other by using a set of events. Each facet MUST define the set of events that the facet supports.

An event MUST consist of the following data elements:

• The name of the event

• The list of arguments with which the event MUST be signaled

This protocol assumes the existence of an implementation-specific communication mechanism used to signal events between facets inside a transaction manager. This communication mechanism MUST NOT allow man-in-the-middle or other classes of intermediary attacks.

Each facet MUST provide a definition for the Name and Enlistment Object.Identifier fields of an Enlistment object, as specified in section 3.1.1.

The conceptual model that is described here requires that one and only one thread of operation be active inside the facets that make up the transaction manager.