A transaction inflow is a contract between the resource adapters and Application Server when the message endpoint (Message-driven Bean) on Application Server is involved in a message provider transaction.

The message endpoint (Message-driven Bean) participates in the transaction associated with the transaction identifier of the message provider.

Note that a transaction inflow is only available with the TP1 inbound integrated function.

The following figure shows the procedure for controlling the transaction inflow.

Figure 3-53 Procedure for controlling the transaction inflow

The following points describe the flow of processing in the figure. Note that the item numbers correspond to the numbers in the figure.

1. The EIS sends a message to the TP1 inbound adapter.
2. The TP1 inbound adapter propagates the EIS transaction identifier to the transaction manager.
3. The TP1 inbound adapter executes the Message-driven Bean.
4. An SQL statement is executed from the Message-driven Bean and the DB is updated.
5. After the execution of Message-driven Bean, the TP1 inbound adapter sends the execution results to the EIS.
6. After receiving the execution results, the EIS sends the instruction to conclude the transaction to the TP1 inbound adapter.
7. The TP1 inbound adapter sends the instruction to conclude the transaction to the transaction manager.
8. The transaction is concluded.