A . If the Pull TIP Transaction event is signaled, the MUST perform the following actions: If the durable log of the is too full<8> to accept the provided transaction object: Signal the event on itself by using the following arguments: The transaction object The error reason code Using implementation-specific functionality, perform the of the that is identified by the that is specified by the RemoteTipTransactionUrl field of the transaction. If the TIP pull propagation operation is successful: Create a new enlistment object (as specified in section 3.1.3.1) by using the following values: TIP interoperability provider role as the Transaction Manager Facet, as specified in section . The transaction object. A null object. Signal the Create Transaction event (as specified in [MS-DTCO] section 3.2.7.13) on the Core Transaction Manager Facet using the following arguments: The Enlistment object. Otherwise, if the TIP pull propagation operation fails: Signal the TIP pull failure event on itself using the following arguments: The transaction object. A reason code that matches the cause of the failure, as follows: TIP Connect Error: If the failure was caused by a connectivity issue. Not Pulled: If the against which the pull was performed, replied with NOTPULLED. (For more information, see section 13.) TIP Error: If any other failure occurred. Push TIP Transaction The Push TIP Transaction event MUST be signaled by using the following arguments: A . An object that contains the contact information of the against which to push the . If the Push TIP transaction event is signaled, the interoperability provider MUST perform the following actions: Construct an object from the Identifier field of the transaction for which the was requested, and set the OurTipTxId field of the transaction object to be the OLETX_TIP_TX_ID object. The format of the szTxId field in the OLETX_TIP_TX_ID structure SHOULD be the nonstandard form of TIP transaction identifier formats specified in section 8. Optionally, the TIP Interoperability Provider
A . If the Pull TIP Transaction event is signaled, the MUST perform the following actions: If the durable log of the is too full<8> to accept the provided transaction object: Signal the event on itself by using the following arguments: The transaction object The error reason code Using implementation-specific functionality, perform the of the that is identified by the that is specified by the RemoteTipTransactionUrl field of the transaction. If the TIP pull propagation operation is successful: Create a new enlistment object (as specified in section 3.1.3.1) by using the following values: TIP interoperability provider role as the Transaction Manager Facet, as specified in section . The transaction object. A null object. Signal the Create Transaction event (as specified in [MS-DTCO] section 3.2.7.13) on the Core Transaction Manager Facet using the following arguments: The Enlistment object. Otherwise, if the TIP pull propagation operation fails: Signal the TIP pull failure event on itself using the following arguments: The transaction object. A reason code that matches the cause of the failure, as follows: TIP Connect Error: If the failure was caused by a connectivity issue. Not Pulled: If the against which the pull was performed, replied with NOTPULLED. (For more information, see section 13.) TIP Error: If any other failure occurred. Push TIP Transaction The Push TIP Transaction event MUST be signaled by using the following arguments: A . An object that contains the contact information of the against which to push the . If the Push TIP transaction event is signaled, the interoperability provider MUST perform the following actions: Construct an object from the Identifier field of the transaction for which the was requested, and set the OurTipTxId field of the transaction object to be the OLETX_TIP_TX_ID object. The format of the szTxId field in the OLETX_TIP_TX_ID structure SHOULD be the nonstandard form of TIP transaction identifier formats specified in section 8. Optionally, the TIP Interoperability Provider
%5BMS-DTCM%5D-170601.docx