TIP Usage Scenario 2
Applies To: Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server Technical Preview, Windows Vista
In this scenario, a client application requests work from a server application in the scope of a transaction. The client application uses a non-DTC transaction manager that supports the TIP protocol. The server application uses the DTC as its transaction manager. The TIP transaction URL of the transaction that is to scope the work is sent with the work request. The following steps are required to create a transaction object and enlist in that transaction:
The server receives a work request from the client. This work request contains a TIP transaction URL that identifies the transaction that should scope the work.
The server calls ITipHelper::Pull, passing in the TIP transaction URL that it received in step 1. If the TIP transaction URL refers to a transaction on TM-X, TM-Y sends a TIP "PULL" command to TM-X if the transaction doesnt already exist in its data structures. The server receives an ITransaction pointer to the transaction object created in TM-Y when the pull completes.
The server calls IResourceManager::Enlist to enlist in the transaction.
If the client-server protocol uses the push model, the client requires the server to identify its transaction manager by using the TIP transaction manager URL format. The client uses this URL to push the transactions before work requests are sent to the server. The following steps show how the server gets the TIP transaction manager URL:
The server receives a request from the client asking it to send the TIP transaction manager URL of the servers transaction manager.
The server gets a pointer to the ITipHelper interface on the core transaction manager object.
The server calls GetLocalTmUrl to get the TIP transaction manager URL for TM-Y.
The server sends the URL it obtained in step 3 back to the client.