5.4.2 Step 2: Define Transaction Policies for the Interfaces

Transaction policies are used on a per-interface basis. During design, it is decided which interfaces within a Oracle Tuxedo CORBA application will handle transactions. The transaction policies are listed in the following table.

Table 5-2 Transaction Policies

Transaction Policy	Description
always	The interface must always be part of a transaction. If the interface is not part of a transaction, a transaction will be automatically started by the TP Framework.
ignore	The interface is not transactional; however, requests made to this interface within a scope of a transaction are allowed. The AUTOTRAN parameter, specified in the UBBCONFIG file for this interface, is ignored.
never	The interface is not transactional. Objects created for this interface can never be involved in a transaction. The Oracle Tuxedo system generates the INVALID_TRANSACTION exception if an interface with this policy is involved in a transaction.
optional	The interface might be transactional. Objects can be involved in a transaction if the request is transactional. This transaction policy is the default. Note: To define transactional properties for a request you can also use the autotran parameter.

During development, you decide which interfaces will execute in a transaction by assigning transaction policies.

For CORBA server applications, you specify transaction policies in the Implementation Configuration File (ICF). A template ICF file is created when you run the genicf command.

In the Transactions sample application, the transaction policy of the Registrar interface is set to always.