In the Adaptive Server plug-in, you can declare EJB Server components to be transactional. When a component is transactional and uses the EJB Server connection management feature, commands sent on a third-tier-database connection are automatically performed as part of a transaction. Component methods can call the EJB Server transaction state primitives to influence whether EJB Server commits or aborts the current transaction.
The component lifecycle is tightly integrated with the EJB Server transaction model. Component instances that participate in a transaction are not deactivated until the transaction ends or until the component indicates that its contribution to the transaction is over (that is, its work is done and ready for commit or that its work must be rolled back). An instance’s time in the active state corresponds to the beginning and end of its participation in a transaction.
