> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aseeflow.org/llms.txt
> Use this file to discover all available pages before exploring further.

# JTA Transaction Integration

### Embedded Process Engine

The process engine transaction management can integrate with JTA and Jakarta Transactions.
To use transaction manager integration, you need to use the

* `org.camunda.bpm.engine.impl.cfg.JtaProcessEngineConfiguration` for JTA integration only.
* `org.camunda.bpm.engine.impl.cfg.JakartaTransactionProcessEngineConfiguration` for Jakarta Transactions integration only.
* `org.camunda.bpm.engine.cdi.CdiJtaProcessEngineConfiguration` for additional CDI expression resolution support.

The process engine requires access to an implementation of `javax.transaction.TransactionManager` or `jakarta.transaction.TransactionManager` respectively.
To achieve JTA transaction integration on these containers, users should use the Spring Framework Abstraction and configure the process engine using the
[SpringProcessEngineConfiguration](/user-guide/spring-framework-integration).

<Warning>
  When you configure a transaction manager, make sure that it actually manages the data source that
  you have configured for the process engine. If that is not the case, the data source works in auto-commit mode.
  This can lead to inconsistencies in the database, because transaction commits and rollbacks are no longer performed.
</Warning>

### Shared Process Engine

The shared process engine distributions for Java EE and Jakarta EE Application Servers (Wildfly, JBoss EAP)
provide JTA or Jakarta Transactions integration out of the box.

### Example

The following example shows how to integrate your custom business logic into a transaction of the process engine:

```java theme={null}
@Named
@Dependent
public class MyBean {

  @Inject
  public RuntimeService runtimeService;

  @Transactional
  public void doSomethingTransactional() {
    // Here you can do transactional stuff in your domain model and it will be 
    // combined in the same transaction as the the following RuntimeService API 
    // call to start a process instance:
    runtimeService.startProcessInstanceByKey("my-process");
  }

}
```