Red Hat JBoss Enterprise Application Platform Administration I

An XA data source can participate in a transaction that spans multiple resources, such as a database, a message queue, and legacy systems. If a problem occurs, then the XA transaction can roll back any changes made.

The following XML shows a PostgreSQL XA data source:

<datasources>
<datasources>
  <xa-datasource jndi-name="java:jboss/PostgresXADS" pool-name="PostgresXADS">
    <xa-datasource-property name="ServerName"> 
      localhost
    </xa-datasource-property>
    <xa-datasource-property name="PortNumber"> 
      5432
    </xa-datasource-property>
    <xa-datasource-property name="DatabaseName"> 
      postgresdb
    </xa-datasource-property>
    <driver>postgresql</driver>
    <security>
      <user-name>admin</user-name>
      <password>admin</password>
    </security>
    <validation>...</validation>
  </xa-datasource>
  <drivers>
    <driver name="postgresql" module="com.postgresql">
      <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class> 
    </driver>
  </drivers>
</datasources>

The following management CLI command creates an XA data source:

[connected /] xa-data-source add \
--name=internal_datasource_name \
-jndi-name=jndi_name --driver-name=driver_name \
--user-name=login --password=password \
--xa-datasource-properties={"ServerName"=>"server",\
"DatabaseName"=>"db_name"}

Compared to defining a non-XA datasource, the XA datasource might require properties such as ServerName, PortNumber and DatabaseName. This depends on the driver in use, but it is required that you provide at least one XA datasource property. For example, the MariaDB connector version 3, requires only the Url property with the connection string.

The driver for the database can be used for both XA and non-XA data sources

The following CLI command registers the driver with a specified XA data source class:

/subsystem=datasources/jdbc-driver=mysql:add(driver-name=name,driver-module-name=module,driver-xa-datasource-class-name=xa_class)

The following management CLI command adds a MariaDB driver specifying the driver class to use with XA and non-XA transactions:

[connected /] /subsystem=datasources/jdbc-driver=mysql:add\
(driver-name=mysql,\
driver-module-name=com.mysql,\
driver-class=org.mariadb.jdbc.Driver,\
driver-xa-datasource-class-name=org.mariadb.jdbc.MariaDbDataSource)