Skip to end of metadata
Go to start of metadata

Datasources are configured through the datasource subsystem. Declaring a new datasource consists of two separate steps: You would need to provide a JDBC driver and define a datasource that references the driver you installed. 

JDBC Driver Installation

The recommended way to install a JDBC driver into WildFly 8 is to deploy it as a regular JAR deployment.  The reason for this is that when you run WildFly in domain mode, deployments are automatically propagated to all servers to which the deployment applies; thus distribution of the driver JAR is one less thing for you to worry about!

Any JDBC 4-compliant driver will automatically be recognized and installed into the system by name and version. A JDBC JAR is identified using the Java service provider mechanism. Such JARs will contain a text a file named META-INF/services/java.sql.Driver, which contains the name of the class(es) of the Drivers which exist in that JAR. If your JDBC driver JAR is not JDBC 4-compliant, it can be made deployable in one of a few ways.

Modify the JAR

The most straightforward solution is to simply modify the JAR and add the missing file. You can do this from your command shell by:

  1. Change to, or create, an empty temporary directory.
  2. Create a META-INF subdirectory.
  3. Create a META-INF/services subdirectory.
  4. Create a META-INF/services/java.sql.Driver file which contains one line - the fully-qualified class name of the JDBC driver.
  5. Use the jar command-line tool to update the JAR like this:

For a detailed explanation how to deploy JDBC 4 compliant driver jar, please refer to the chapter "Application Deployment".

Datasource Definitions

The datasource itself is defined within the subsystem datasources:

(See standalone/configuration/standalone.xml)

As you can see the datasource references a driver by it's logical name.

You can easily query the same information through the CLI:

Using the web console or the CLI greatly simplifies the deployment of JDBC drivers and the creation of datasources.

The CLI offers a set of commands to create and modify datasources:

Using security domains

Information can be found at

Component Reference

The datasource subsystem is provided by the IronJacamar project. For a detailed description of the available configuration properties, please consult the project documentation.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. May 09, 2014

    In the example, the h2 driver is used, and the driver-name=h2 so its easy to define a datasource. 

    I found no way to set the driver-name on deploy of a jdbc driver other than editing the standalone.xml file. I understood this is not the way to go and it is recommended to use the web console or the cli to manipulate the standalone.xml.

    I'm using the cli comman 'deploy <file> --name <driver-name>' .

    In jboss 7.x, this would set the driver-name correctly, in wildfly 8.x it does not. In wildfly, it sets the runtime-name, but this is not used when defining a datasource. A datasource needs a correctly set driver-name.

    I tested this on 8.0.0Final and 8.1.0CR1.

    Is this a bug or am I doing something wrong ?

    1. May 09, 2014

      Please file jira bug report and we can go on from there.