[ https://issues.jboss.org/browse/TEIID-4311?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4311: ------------------------------------- This may be straight forward as others. To find out a JDBC driver supports the XA connection, on the call {code} [standalone@localhost:9999 /] /subsystem=datasources:installed-drivers-list { "outcome" => "success", "result" => [ { "driver-name" => "teiid-local", "deployment-name" => undefined, "driver-module-name" => "org.jboss.teiid", "module-slot" => "main", "driver-datasource-class-name" => "", "driver-xa-datasource-class-name" => "org.teiid.jdbc.TeiidDataSource", "driver-class-name" => "org.teiid.jdbc.TeiidDriver", "driver-major-version" => 8, "driver-minor-version" => 12, "jdbc-compliant" => false } } {code} You need to make sure "driver-xa-datasource-class-name" property exists with valid name. Now based on this, we need to introduce an extra template name with "xa-" as post fix The template definition properties for this "xa" template, we need to add three extra properties {code} ServerName PortNumber DatabaseName {code} Now, when a user calls "createDatasource", with this new template you will know it is XA connection based on template name or an extra property in it. Now coming down to setting "xa-datasource-properties", there is property called "connection-properties" you need to use that. See, how this is used in the driver creation, we need to re-purpose this property. As these require multiple executions run them in batch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)