Datasource Management

Type

Datasources (non-XA) - for applications that do not use transactions or use transactions with a single database

XA datasources - transactions are distributed across multiple databases

Example datasource

provided at "java:jboss/datasources/ExampleDS"

Deployment of -ds.xml files

(not recommended for production environments)

*-ds.xml in deployment directory, not required but supported.

JDBC driver

Install with management console:

• download JAR
• on management console:
  • Runtime -> Server -> Manage Deployments
  • En/Disable

Preferred method: install as a core module

• download
• create file path structure under EAP_HOME_Modules (for example, EAP_HOME/modules/com/mysql/main)
• copy driver JAR into main/
• create module.xml in main/ (XSD: EAP_HOME/docs/schema/module-1_2.xsd)

Example:

<?xml version="1.0" encoding="UTF-8"?> <module xmlns="urn:jboss:module:1.0" name="com.mysql"> <resources> <resource-root path="mysql-connector-java-5.1.15.jar"/> </resources> <dependencies> <module name="javax.api"/> <module name="javax.transaction.api"/> </dependencies> </module>

• start server
• start management CLI
• use command:

/subsystem=datasources/jdbc-driver=DRIVER_NAME:add(driver-name=DRIVER_NAME,driver-module-name=MODULE_NAME,driver-xa-datasource-class-name=XA_DATASOURCE_CLASS_NAME)

/subsystem=datasources/jdbc-driver=mysql:add(driver-name=mysql,driver-module-name=com.mysql,driver-xa-datasource-class-name=com.mysql.jdbc.jdbc2.optional.MysqlXADataSource)

Create Non-XA Datasource with Management Interfaces

With CLI:

data-source add --name=DATASOURCE_NAME --jndi-name=JNDI_NAME --driver-name=DRIVER_NAME  --connection-url=CONNECTION_URL

data-source enable --name=DATASOURCE_NAME

Management Console:

Profile -> Datasources

• Name: any name
• JNDI: (example) "java:jboss/datasources/NameOfDataSource"
• Driver: choose (may need to install first)
• URL / user name / password
• parameter: spy - enable JDBC logging, logging-category parameter must be set to "org.jboss.jdbc"
• jta

Datasource security

Preferred solution is either Security Domain or Password Vaults, further study needed

Enable JTA (for non-XA datasource)

(see transaction subsystem)

For standalone server:

edit EAP_HOME/standalone/configuration/standalone.xml, locate <datasource> tag and add / change attribute jta="true", restart server

Or use management console

Other details

Very detailed other properties and samples for popular databases are provided in the reference