11.6.2. Transactional Datasource Configuration

Summary

This task shows you how to enable Java Transaction API (JTA) on your datasource.

Prerequisites

You must meet the following conditions before continuing with this task:

Your database or other resource must support Java Transaction API. If in doubt, consult the documentation for your database or other resource.
Create a datasource. Refer to Section 11.6.2.4, “Create a Non-XA Datasource with the Management Interfaces”.
Stop JBoss EAP 6.
Have access to edit the configuration files directly, in a text editor.

Procedure 11.1. Configure the Datasource to use Java Transaction API

Open the configuration file in a text editor.
Depending on whether you run JBoss EAP 6 in a managed domain or standalone server, your configuration file will be in a different location.
- Managed domain
  The default configuration file for a managed domain is in EAP_HOME/domain/configuration/domain.xml for Red Hat Enterprise Linux, and EAP_HOME\domain\configuration\domain.xml for Microsoft Windows Server.
- Standalone server
  The default configuration file for a standalone server is in EAP_HOME/standalone/configuration/standalone.xml for Red Hat Enterprise Linux, and EAP_HOME\standalone\configuration\standalone.xml for Microsoft Windows Server.
Locate the <datasource> tag that corresponds to your datasource.
The datasource will have the jndi-name attribute set to the one you specified when you created it. For example, the ExampleDS datasource looks like this:
```
<datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="H2DS" enabled="true" jta="true" use-java-context="true" use-ccm="true">
```
Set the jta attribute to true.
Add the following to the contents of your <datasource> tag, as they appear in the previous step: jta="true"
Save the configuration file.
Save the configuration file and exit the text editor.
Start JBoss EAP 6.
Relaunch the JBoss EAP 6 server.

Result:

JBoss EAP 6 starts, and your datasource is configured to use Java Transaction API.