5.2 What Happens During a Transaction

The following figure illustrates how transactions work in a Oracle Tuxedo CORBA application.

Figure 5-1 How Transactions Work in a Oracle Tuxedo CORBA Application

A basic transaction works in the following way:

1. The client application uses the Bootstrap object to return an object reference to the TransactionCurrent object for the Oracle Tuxedo domain.
2. A client application begins a transaction using the Tobj::TransactionCurrent::begin() method, and issues a request to the CORBA interface through the TP Framework. All operations on the CORBA interface execute within the scope of a transaction.
   • If a call to any of these operations raises an exception (either explicitly or as a result of a communication failure), the exception can be caught and the transaction can be rolled back.
   • If no exceptions occur, the client application commits the current transaction using the Tobj::TransactionCurrent::commit() method. This method ends the transaction and starts the processing of the operation. The transaction is committed only if all of the participants in the transaction agree to commit.
3. The Tobj::TransactionCurrent:commit() method causes the TP Framework to call the Transaction Manager to complete the transaction.
4. The Transaction Manager updates the database.

Note:

Oracle Tuxedo CORBA also supports the use of the CORBA Interoperable Naming Service (INS) to obtain an initial object reference for the Security Service. For information on the INS bootstrapping mechanism, see the CORBA Programming Reference.