Example Datasources

6.7.1. Example PostgreSQL Datasource

Example 6.8.

The example below is a PostgreSQL datasource configuration. The datasource has been enabled, a user has been added, and validation options have been set.

<datasources>

<datasource jndi-name="java:jboss/PostgresDS" pool-name="PostgresDS">

<connection-url>jdbc:postgresql://localhost:5432/postgresdb</connection-url>

<driver>postgresql</driver>

<security>

<user-name>admin</user-name>

<password>admin</password>

</security>

<validation>

<valid-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChe cker"></valid-connection-checker>

<exception-sorter

class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"><

/exception-sorter>

</validation>

</datasource>

<drivers>

<driver name="postgresql" module="org.postgresql">

<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>

</driver>

</drivers>

</datasources>

The example below is a module.xml file for the PostgreSQL datasource above.

<module xmlns="urn:jboss:module:1.1" name="org.postgresql">

<resources>

<resource-root path="postgresql-9.1-902.jdbc4.jar"/>

</resources>

<dependencies>

<module name="javax.api"/>

<module name="javax.transaction.api"/>

</dependencies>

</module>

Report a bug

Example 6.9.

The example below is a PostgreSQL XA datasource configuration. The datasource has been enabled, a user has been added, and validation options have been set.

<datasources>

<xa-datasource jndi-name="java:jboss/PostgresXADS" pool-name="PostgresXADS">

<driver>postgresql</driver>

<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>

<security>

<user-name>admin</user-name>

<password>admin</password>

</security>

<validation>

<valid-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChe cker">

</valid-connection-checker>

<exception-sorter

class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter">

</exception-sorter>

</validation>

</xa-datasource>

<drivers>

<driver name="postgresql" module="org.postgresql">

<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>

</driver>

</drivers>

</datasources>

The example below is a module.xml file for the PostgreSQL XA datasource above.

<module xmlns="urn:jboss:module:1.1" name="org.postgresql">

<resources>

<resource-root path="postgresql-9.1-902.jdbc4.jar"/>

</resources>

<dependencies>

<module name="javax.api"/>

<module name="javax.transaction.api"/>

</dependencies>

</module>

Report a bug

6.7.3. Example MySQL Datasource

Example 6.10.

The example below is a MySQL datasource configuration. The datasource has been enabled, a user has been added, and validation options have been set.

<datasources>

<datasource jndi-name="java:jboss/MySqlDS" pool-name="MySqlDS">

<connection-url>jdbc:mysql://mysql-localhost:3306/jbossdb</connection-url>

<driver>mysql</driver>

<security>

<user-name>admin</user-name>

<password>admin</password>

</security>

<validation>

<valid-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"></

valid-connection-checker>

<exception-sorter

class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"></except ion-sorter>

</validation>

</datasource>

<drivers>

<driver name="mysql" module="com.mysql">

<xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>

</driver>

</drivers>

</datasources>

The example below is a module.xml file for the MySQL datasource above.

<module xmlns="urn:jboss:module:1.1" name="com.mysql">

<resources>

<resource-root path="mysql-connector-java-5.0.8-bin.jar"/>

</resources>

<dependencies>

<module name="javax.api"/>

<module name="javax.transaction.api"/>

</dependencies>

</module>

Report a bug

6.7.4 . Example MySQL XA Datasource

Example 6.11.

The example below is a MySQL XA datasource configuration. The datasource has been enabled, a user has been added, and validation options have been set.

<datasources>

<xa-datasource jndi-name="java:jboss/MysqlXADS" pool-name="MysqlXADS">

<driver>mysql</driver>

<xa-datasource-property name="ServerName">localhost</xa-datasource-property>

<xa-datasource-property name="DatabaseName">mysqldb</xa-datasource-property>

<security>

<user-name>admin</user-name>

<password>admin</password>

</security>

<validation>

<valid-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"></

valid-connection-checker>

<exception-sorter

class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"></except ion-sorter>

</validation>

</xa-datasource>

<drivers>

<driver name="mysql" module="com.mysql">

<xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>

</driver>

</drivers>

</datasources>

The example below is a module.xml file for the MySQL XA datasource above.

<module xmlns="urn:jboss:module:1.1" name="com.mysql">

<resources>

<resource-root path="mysql-connector-java-5.0.8-bin.jar"/>

</resources>

<dependencies>

<module name="javax.api"/>

<module name="javax.transaction.api"/>

</dependencies>

</module>

Report a bug

6.7.5. Example Oracle Datasource

Oracle Datasources

Prior to version 10.2 of the Oracle datasource, the <no-tx-separate-pools/> parameter was required, as mixing non-transactional and transactional connections would result in an error. This parameter may no longer be required for certain applications.

Example 6.12.

The example below is an Oracle datasource configuration. The datasource has been enabled, a user has been added, and validation options have been set.

<datasources>

<datasource jndi-name="java:/OracleDS" pool-name="OracleDS">

<connection-url>jdbc:oracle:thin:@localhost:1521:XE</connection-url>

<driver>oracle</driver>

<security>

<user-name>admin</user-name>

<password>admin</password>

</security>

<validation>

<valid-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker">

</valid-connection-checker>

<stale-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker">

<driver name="oracle" module="com.oracle">

<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>

</driver>

</drivers>

</datasources>

The example below is a module.xml file for the Oracle datasource above.

<module xmlns="urn:jboss:module:1.1" name="com.oracle">

<resources>

<resource-root path="ojdbc6.jar"/>

</resources>

<dependencies>

<module name="javax.api"/>

<module name="javax.transaction.api"/>

</dependencies>

</module>

Report a bug

6.7.6. Example Oracle XA Datsource

Oracle Datasources

Prior to version 10.2 of the Oracle datasource, the <no-tx-separate-pools/> parameter was required, as mixing non-transactional and transactional connections would result in an error. This parameter may no longer be required for certain applications.

Important

The following settings must be applied for the user accessing an Oracle XA datasource in order for XA recovery to operate correctly:

GRANT SELECT ON sys.dba_pending_transactions TO user;

GRANT SELECT ON sys.pending_trans$ TO user;

GRANT SELECT ON sys.dba_2pc_pending TO user;

GRANT EXECUTE ON sys.dbms_xa TO user;

Example 6.13.

The example below is an Oracle XA datasource configuration. The datasource has been enabled, a user has been added, and validation options have been set.

<datasources>

<xa-datasource jndi-name="java:/XAOracleDS" pool-name="XAOracleDS">

<driver>oracle</driver>

<xa-datasource-property name="URL">jdbc:oracle:oci8:@tc</xa-datasource-property>

<security>

<user-name>admin</user-name>

<password>admin</password>

</security>

<xa-pool>

<is-same-rm-override>false</is-same-rm-override>

<no-tx-separate-pools />

</xa-pool>

<validation>

<valid-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker">

</valid-connection-checker>

<stale-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker">

</stale-connection-checker>

<exception-sorter

class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"></exce ption-sorter>

</validation>

</xa-datasource>

<drivers>

<driver name="oracle" module="com.oracle">

<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>

</driver>

</drivers>

</datasources>

The example below is a module.xml file for the Oracle XA datasource above.

<module xmlns="urn:jboss:module:1.1" name="com.oracle">

<resources>

<resource-root path="ojdbc6.jar"/>

</resources>

<dependencies>

<module name="javax.api"/>

<module name="javax.transaction.api"/>

</dependencies>

</module>

Report a bug

6.7.7. Example Microsoft SQLServer Datasource

Example 6.14 .

The example below is a Microsoft SQLServer datasource configuration. The datasource has been enabled, a user has been added, and validation options have been set.

<datasources>

<datasource jndi-name="java:/MSSQLDS" pool-name="MSSQLDS">

<connection-url>jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=MyDatabase</connection -url>

<driver>sqlserver</driver>

<security>

<user-name>admin</user-name>

<password>admin</password>

</security>

<validation>

<valid-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.mssql.MSSQLValidConnectionChecker"></

valid-connection-checker>

</validation>

</datasource>

<drivers>

<driver name="sqlserver" module="com.microsoft">

<xa-datasource-class>com.microsoft.sqlserver.jdbc.SQLServerXADataSource</xa-datasource-class>

</driver>

</datasources>

The example below is a module.xml file for the Microsoft SQLServer datasource above.

<module xmlns="urn:jboss:module:1.1" name="com.microsoft">

<resources>

<resource-root path="sqljdbc4.jar"/>

</resources>

<dependencies>

<module name="javax.api"/>

<module name="javax.transaction.api"/>

</dependencies>

</module>

Report a bug

6.7.8. Example Microsoft SQLServer XA Datasource

Example 6.15.

The example below is a Microsoft SQLServer XA datasource configuration. The datasource has been enabled, a user has been added, and validation options have been set.

<datasources>

<xa-datasource jndi-name="java:/MSSQLXADS" pool-name="MSSQLXADS">

<driver>sqlserver</driver>

<xa-datasource-property name="ServerName">localhost</xa-datasource-property>

<xa-datasource-property name="DatabaseName">mssqldb</xa-datasource-property>

<xa-datasource-property name="SelectMethod">cursor</xa-datasource-property>

<security>

<user-name>admin</user-name>

<password>admin</password>

</security>

<xa-pool>

<is-same-rm-override>false</is-same-rm-override>

</xa-pool>

<validation>

<valid-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.mssql.MSSQLValidConnectionChecker"></

valid-connection-checker>

</validation>

</xa-datasource>

<drivers>

<driver name="sqlserver" module="com.microsoft">

<xa-datasource-class>com.microsoft.sqlserver.jdbc.SQLServerXADataSource</xa-datasource-class>

</driver>

</drivers>

</datasources>

The example below is a module.xml file for the Microsoft SQLServer XA datasource above.

<module xmlns="urn:jboss:module:1.1" name="com.microsoft">

<resources>

<resource-root path="sqljdbc4.jar"/>

</resources>

<dependencies>

<module name="javax.api"/>

<module name="javax.transaction.api"/>

</dependencies>

</module>

Report a bug

6.7.9. Example IBM DB2 Datasource

Example 6.16.

The example below is an IBM DB2 datasource configuration. The datasource has been enabled, a user has been added, and validation options have been set.

<datasources>

<datasource jndi-name="java:/DB2DS" pool-name="DB2DS">

<connection-url>jdbc:db2:ibmdb2db</connection-url>

<driver>ibmdb2</driver>

<pool>

<min-pool-size>0</min-pool-size>

<max-pool-size>50</max-pool-size>

</pool>

<security>

<user-name>admin</user-name>

<password>admin</password>

</security>

<validation>

<valid-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.db2.DB2ValidConnectionChecker"></vali d-connection-checker>

<stale-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.db2.DB2StaleConnectionChecker"></stal e-connection-checker>

<exception-sorter

class- name="org.jboss.jca.adapters.jdbc.extensions.db2.DB2ExceptionSorter"></exception-sorter>

</validation>

</datasource>

<drivers>

<driver name="ibmdb2" module="com.ibm">

<xa-datasource-class>com.ibm.db2.jdbc.DB2XADataSource</xa-datasource-class>

</driver>

</drivers>

</datasources>

The example below is a module.xml file for the IBM DB2 datasource above.

<module xmlns="urn:jboss:module:1.1" name="com.ibm">

<resources>

<resource-root path="db2jcc.jar"/>

</resources>

<dependencies>

<module name="javax.api"/>

<module name="javax.transaction.api"/>

</dependencies>

</module>

Report a bug

6.7.10. Example IBM DB2 XA Datasource

Example 6.17.

The example below is an IBM DB2 XA datasource configuration. The datasource has been enabled, a user has been added and validation options have been set.

<datasources>

<xa-datasource jndi-name="java:/DB2XADS" pool-name="DB2XADS">

<driver>ibmdb2</driver>

<xa-datasource-property name="DatabaseName">ibmdb2db</xa-datasource-property>

<security>

<user-name>admin</user-name>

<password>admin</password>

</security>

<xa-pool>

<is-same-rm-override>false</is-same-rm-override>

</xa-pool>

<validation>

<valid-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.db2.DB2ValidConnectionChecker"></vali d-connection-checker>

<stale-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.db2.DB2StaleConnectionChecker"></stal

<config-property name="EnableIsValid">false</config-property>

<config-property name="IsValidOverride">false</config-property>

<config-property name="EnableClose">false</config-property>

</recovery-plugin>

</recovery>

</xa-datasource>

<drivers>

<driver name="ibmdb2" module="com.ibm">

<xa-datasource-class>com.ibm.db2.jdbc.DB2XADataSource</xa-datasource-class>

</driver>

</drivers>

</datasources>

The example below is a module.xml file for the IBM DB2 XA datasource above.

<module xmlns="urn:jboss:module:1.1" name="com.ibm">

<resources>

<resource-root path="db2jcc.jar"/>

</resources>

<dependencies>

<module name="javax.api"/>

<module name="javax.transaction.api"/>

</dependencies>

</module>

Report a bug

6.7.11. Example Sybase Datasource

Example 6.18.

The example below is a Sybase datasource configuration. The datasource has been enabled, a user has been added, and validation options have been set.

<datasources>

<datasource jndi-name="java:jboss/SybaseDB" pool-name="SybaseDB"

enabled="true">

<connection-url>jdbc:sybase:Tds:localhost:5000/DATABASE?

JCONNECT_VERSION=6</connection-url>

<security>

<user-name>admin</user-name>

<password>admin</password>

</security>

<validation>

<valid-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.sybase.SybaseValidConnectionChecker">

</valid-connection-checker>

<exception-sorter

class-name="org.jboss.jca.adapters.jdbc.extensions.sybase.SybaseExceptionSorter"></excep tion-sorter>

</validation>

</datasource>

<drivers>

<driver name="sybase" module="com.sybase">

<datasource-class>com.sybase.jdbc2.jdbc.SybDataSource</datasource-class>

<xa-datasource-class>com.sybase.jdbc3.jdbc.SybXADataSource</xa-datasource-class>

</driver>

</drivers>

</datasources>

The example below is a module.xml file for the Sybase datasource above.

<module xmlns="urn:jboss:module:1.1" name="com.sybase">

<resources>

<resource-root path="jconn2.jar"/>

</resources>

<dependencies>

<module name="javax.api"/>

<module name="javax.transaction.api"/>

</dependencies>

</module>

Report a bug

6.7.12. Example Sybase XA Datasource

Example 6.19.

The example below is a Sybase XA datasource configuration. The datasource has been enabled, a user has been added, and validation options have been set.

<datasources>

<xa-datasource jndi-name="java:jboss/SybaseXADS" pool-name="SybaseXADS"

enabled="true">

<xa-datasource-property name="NetworkProtocol">Tds</xa-datasource-property>

<xa-datasource-property name="ServerName">myserver</xa-datasource-property>

<xa-datasource-property name="PortNumber">4100</xa-datasource-property>

<xa-datasource-property name="DatabaseName">mydatabase</xa-datasource-property>

<security>

<user-name>admin</user-name>

<password>admin</password>

</security>

<validation>

<valid-connection-checker

class-name="org.jboss.jca.adapters.jdbc.extensions.sybase.SybaseValidConnectionChecker">

</valid-connection-checker>

<exception-sorter

class-name="org.jboss.jca.adapters.jdbc.extensions.sybase.SybaseExceptionSorter"></excep

class-name="org.jboss.jca.adapters.jdbc.extensions.sybase.SybaseExceptionSorter"></excep

In document JBoss - JBoss EAP 6 Administration and Configuration Guide (Page 101-113)