4.2.3 Receiving the TXUSER_TIPPROXYGATEWAY_MTAG_PUSHED Message

  • Article

When the TIP interoperability provider receives the TXUSER_TIPPROXYGATEWAY_MTAG_PUSH2 message from the application, it attempts to perform the TIP push propagation of the transaction to the TIP transaction manager URL that is specified in the message. If the push completes successfully, the TIP interoperability provider enlists as a subordinate in the transaction and sends a TXUSER_TIPPROXYGATEWAY_MTAG_PUSHED message to the TIP interoperability application.

The tipTxId field in the message is set to represent the TIP identifier of the transaction that is created by the TIP transaction manager as a result of the push propagation ("OleTx-757fda7b-aa73-4179-aa55-131b22c43db5" in this case). Each field in the message aligns to a multiple of 4 bytes. The following table presents the layout of the TXUSER_TIPPROXYGATEWAY_MTAG_PUSHED message:

 Field

 Value

 Description

MsgTag

0x00000FFF

MTAG_USER_MESSAGE

fIsMaster

0x00000000

0

dwConnectionId

0x00000001

1

dwUserMsgType

0x00005106

TXUSER_TIPPROXYGATEWAY_MTAG_PUSHED

dwcbVarLenData

0x00000034

52

dwReserved1

0xcd64cd64

dwReserved1: 0xcd64cd64

tipTxId

0x00000001

0x0000002b

0x54656c4f

0x35372d78

0x61646637

0x612d6237

0x2d333761

0x39373134

0x3561612d

0x33312d35

0x32326231

0x64333463

0x00003562

lVersion: 1

cbTxId: 43

szTxId: "OleTx-757fda7b-aa73-4179-aa55-131b22c43db5"

Padding: 00

After the TIP interoperability application receives the TXUSER_TIPPROXYGATEWAY_MTAG_PUSHED message, no more user messages can be sent over this connection, and the application initiates the disconnect sequence.