Overview of Transactions

In ActiveMatrix BusinessWorks a transaction is a logical unit of work. Transactions allow you to group multiple activities into an atomic execution unit. All activities that can participate in a transaction must either complete successfully or be undone or rolled back together. To create a transaction, you use a group to surround the activities in the transaction.

Not all ActiveMatrix BusinessWorks activities can participate in a transaction. Only the following types of activities have transactional capabilities:

  • JDBC activities

  • JMS activities

  • ActiveEnterprise Adapter activities that use JMS transports

  • EJB activities

  • TIBCO iProcess BusinessWorks Connector activities

Although only the activities above can be part of a transaction, any activity can be contained in a transaction group. For example, you may have three JDBC Update activities and one Write File activity in a transaction group. All the JDBC Update activities either complete or roll back at the end of the transaction. The Write File activity, however, does not participate in the transaction and executes whether the transaction commits or fails.

For more information about creating groups, see Grouping Activities.