Transaction Properties
This section describes custom engine properties that can be set for the resources in the Transaction palette.
bw.plugin.transaction.xa.arjuna.objectStoreDir
By default, when executing the Arjuna Transaction Service within the same JVM as ActiveMatrix BusinessWorks, the Arjuna property file is used to determine the location of the object store directory. If you wish to override the value in the Arjuna property file, set the custom engine property bw.plugin.transaction.xa.arjuna.objectStoreDir
to a valid directory name.
bw.plugin.transaction.xa.isolation
By default in an XA transaction, the transaction isolation level is set to the default value for the JDBC driver you are using. If you wish to ensure a particular transaction isolation level, set the bw.plugin.transaction.xa.isolation
custom engine property to one of the following values:
Value |
Transaction Isolation Level Description |
1 |
java.sql.Connection.TRANSACTION_READ_UNCOMMITTED |
2 |
java.sql.Connection.TRANSACTION_READ_COMMITTED |
3 |
java.sql.Connection.TRANSACTION_REPEATABLE_READ |
4 |
java.sql.Connection.TRANSACTION_SERIALIZABLE |
bw.plugin.transaction.xa.lock.connection
By default, JDBC activities in an XA Transaction groups obtain database connections from a connection pool and release the connections when the activity completes. This can cause a database connection to be used concurrently in multiple transactions. Some databases or JDBC drivers support this behavior and others do not. If you are using a database or JDBC driver that requires database connections to be used in only one transaction at a time (for example, IBM DB2), set the bw.plugin.transaction.xa.lock.connection
custom engine property to true
. When the value of this property is set to true
, once a connection is associated with a transaction, the connection remains associated with the transaction until the transaction completes. The default value of this property is false
.