Transaction | X4Documentation

Transaction: Executes process actions as transaction: On a Commit, all operations are applied to the target system. On a Rollback, all operations are reset to the original state before the transaction. To encapsulate process actions into a transaction, place the corresponding transaction components before and after the process actions. In most cases, the transaction component is used for JMS queue operations and for database operations.

Please observe the following notes:

Transactions do not work in the X4 Designer's debug mode.
Transactions only work if the JNDI name of the datasource is provided.
From within a transaction, you can execute subprocesses.
If a subprocess is started from within a transaction using the (7.4.0-en) Process Starter adapter, the transaction does not apply for this subprocess (transactions do not work throughout threads).
It is not possible to nest transactions in transactions.
In a transaction, you can use multiple database connections and JMS queues.
The used database connection (JDBC DataSources) must support transactional handling.
To be able to execute transactions, the jta attribute must not be set to false when configuring the datasource to be used within the standalone.xml.

Properties

Label

Label of the symbol within the process diagram

Operation

Define a transaction operation

Possible values:

Not assigned: no transaction assigned
Begin: begin transaction
Commit: execute/complete transaction
Rollback: cancel transaction and revert the transaction's operations

Status values

`1`	The transaction component was executed successfully.
`0`	The transaction component was executed without result.
`-1`	An error occurred during the transaction.