Data source configuration - application server - 8.x

On this page


Configure data sources describes two ways to configure data sources for the macros provided by SQL for Confluence. This page focuses on application server based data source configurations.

The data source is referenced using the dataSource (Data source name) parameter. The exact configuration of a data source is application server and database specific. A Confluence administrator must configure the data source and the Confluence application server must be restarted for changes to be active. The configuration must be done very carefully as any errors results in the data source being unusable (sad). Each database you need to access in Confluence must have a data source configuration.

These are the major elements of the configuration:

  1. Application server data source configuration - consult your application server documentation on how this is done and problem determination mechanisms. Note that the configuration may be specific to the application server version. For example, older Tomcat versions have some different configurations.
  2. JDBC driver specific for the database to be accessed - consult your database documentation and other sources for the best JDBC driver to use.
  3. Installation of JDBC driver on the application server.
  4. Database access - consult your database documentation on how to configure your database for access.

Various users have provided some examples that covers many standard situations. This page can be used to share that type of information as well as problem determination information. This is the best place to start, especially, if you are not an expert in this area.

Just upgraded Confluence?

A common problem is getting errors after upgrading Confluence. Ensure that your upgrade procedures include updating your server.xml, and, copying all the JDBC drivers you use into the appropriate location. Also, check out this page for isolating these or application server version differences that cause problems. If you get errors immediately after an upgrade, this is the most likely cause.

Updated documentation

This page is updated from a previous version that has been archived as SQL for Confluence datasource configuration. The former page has been kept as a reference for links and comments. Some of the comments are still useful as they represent user questions and user contributed configurations and solutions. However, some of the information is also out dated.

Confluence installation with Tomcat

Many users install the standard Confluence standalone distribution that includes Tomcat. This section discusses configuration specific to this application server environment. The most recent versions of Confluence use newer versions of the Tomcat application server where the following configuration examples apply:

JDBC Driver Location

Put the driver jar in <install-dir>/lib - this is the directory that has other Tomcat jars. If you have a much older version of Confluence that does not have this directory, look for <install-dir>/common/lib instead.

Tomcat configuration

Modify <install-dir>/conf/server.xml to add one or more data source resource elements. server.xml is an example of adding a few data sources for various local and non-local databases.

The essential element is something like the following where the data source name is myDS:

<Resource name="jdbc/myDS"
    validationQuery="Select 1"

Resource must be within the Confluence context tag

<Context path="" docBase="../confluence" debug="0" reloadable="false">
<Resource ... />

Consider using a validation query

Database examples

The sql macro markup looks like: {sql:dataSource=myDS| ... }  

See Data source configuration - application server - Examples - 8.x.

Further configuration management

See How to limit active database connections.

Other databases

Support for other databases depends on the capabilities provided by the JDBC driver. SQL for Confluence expects certain JDBC features to be available. In some cases, parameter choices can affect which capabilities are needed. User testing and community support is about the only help that is available for less popular databases/JDBC drivers. If you have had success with other databases, please add information to this page.

Problem determination

See Data source configuration - problem determination.