3.5.3 Defining an Object’s Activation Policies

As part of CORBA server development, you determine what events cause an object to be activated and deactivated by assigning object activation policies.

For CORBA server applications, specify object activation policies in the Implementation Configuration File (ICF). A template ICF file is created by the genicf command.

Note:

You also define transaction policies in the ICF file. For information about using transactions in your Oracle Tuxedo CORBA application, see Using CORBA Transactions in the Oracle Tuxedo online documentation.

The Oracle Tuxedo software supports the activation policies listed in the following table.

Table 3-4 Activation Policies

Activation Policy	Description
method	Causes the object to be active only for the duration of the invocation on one of the object’s operations. This is the default activation policy.
transaction	Causes the object to be activated when an operation is invoked on it. If the object is activated within the scope of a transaction, the object remains active until the transaction is either committed or rolled back.
process	Causes the object to be activated when an operation is invoked on it, and to be deactivated only when one of the following occurs: The process in which the server application exists is shut down. The method TP::deactivateEnable() (C++) has been invoked on the object.

The Simple interface in the Simpapp sample application is assigned the default activation policy of method. For more information about managing object state and defining object activation policies, see Creating CORBA Server Applications in the Oracle Tuxedo online documentation.