Platform SDK: Transaction Server

Life of a Transaction: Client Application Startup (Phases)

d1 The client calls the DtcGetTransactionManager procedure in the MS DTC proxy. The client may either specify the name and location of the transaction manager it chooses to use or it may specify NULL values for these parameters. Normally, the client specifies NULL values for these parameters. This causes the MS DTC proxy to establish a connection with the default MS DTC transaction manager. The name of the default transaction manager is contained in the system registry. The client also specifies which MS DTC proxy core object interface pointer it chooses to be returned. Normally, the client requests the ITransactionDispenser interface pointer.
d2 The MS DTC proxy creates the MS DTC proxy core object and returns the requested interface pointer to the client. Typically, this is the ITransactionDispenser interface pointer.
d3 The client calls the RM proxy to establish a connection with the resource manager. The syntax of this call is the responsibility of the resource manager developer. The client does this once for each connection it chooses to establish with the resource manager.
d4 The RM proxy establishes a connection to the resource manager. This may involve communication between the RM proxy and the RM that is not depicted here. The RM proxy typically returns a resource manager connection handle to the client. The client uses this handle to communicate with the resource manager.