Configuring JTA UserTransaction Transactions

To configure a JTA UserTransaction, select JTA UserTransaction as the transaction type of the group.

JDBC Connections used by JDBC activities in the transaction group must be configured to use JNDI as the connection type and specify the data source in the application server. Activities that use the JMS transport must be configured to use the XA connection factory in the application server. The JNDI configuration for JMS, EJB, or JDBC activities must specify the appropriate connection and JNDI Context information for the application server.

The JTA UserTransaction transaction group has the following fields on the transaction group’s Configuration tab:

Field

Description

Transaction Manager

A JTA UserTransaction shared configuration resource. For more information about this resource, see TIBCO ActiveMatrix BusinessWorks Palette Reference.

Include Checkpoint

When this field is checked, an implicit checkpoint is performed after the last activity in the group completes successfully and before the transaction is committed. The deployment configuration must specify a database for storing process engine information and the JDBC Connection used must specify JNDI as the connection type for this checkpoint to participate in the transaction.

Checkpoint Duplicate Key

When the Include Checkpoints field is checked, you can specify a duplicate key in this field to perform duplicate checking. This is useful if the checkpoint included in the transaction is the first checkpoint in the process definition. If the process engine crashes after the checkpoint, restarted process instances can use the duplicate key to determine if the transaction has already committed. For more information about specifying duplicate keys, see Detecting Duplicate Process Instances.