This page tells you how to set up a SQL Server datasource connection for Confluence.
Step 1. Shut down Tomcat
Run bin/shutdown.sh or bin/shutdown.bat to bring Tomcat down while you are making these changes.
Make a backup of your /confluence.cfg.xmlfile and your /conf/server.xml file, so that you can easily revert if you have a problem.
Step 2. Install the SQL Server database driver
Download the SQL Server JDBC driver:
Links are available on this page: Database JDBC Drivers.
Unpack the archive file you have downloaded, and find the JAR file called something like this: jtds-x.x.x.jar, where x.x.x is a version number.
Alternatively, you can get the driver from your Confluence installation:/confluence/WEB-INF/lib/jtds-x.x.x.jar.
Put the JAR file into the lib folder of your Tomcat installation:/lib.
Step 3. Configure Tomcat
Edit the conf/server.xml file in your Tomcat installation.
Find the following lines:
Insert the DataSource Resource element inside the Context element, directly after the opening line, ¬†before Manager:
¬†¬†¬†¬†validationQuery="select 1" />
Replace the username and password parameters with the correct values for your database
In the url parameter, replace the word 'yourDatabaseName' with the name of the database your Confluence data will be stored in.
If switching from a direct JDBC connection to datasource, you can find the above details in your/confluence.cfg.xml file.
Here are the configuration properties for Tomcat's standard data source resource factory (org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory):
driverClassName ‚ÄĒ Fully qualified Java class name of the JDBC driver to be used.
maxActive ‚ÄĒ The maximum number of active instances that can be allocated from this pool at the same time.
maxIdle ‚ÄĒ The maximum number of connections that can sit idle in this pool at the same time.
maxWait ‚ÄĒ The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception.
password ‚ÄĒ Database password to be passed to our JDBC driver.
url ‚ÄĒ Connection URL to be passed to our JDBC driver. (For backwards compatibility, the property driverName is also recognized.)
user ‚ÄĒ Database username to be passed to our JDBC driver.
validationQuery ‚ÄĒ SQL query that can be used by the pool to validate connections before they are returned to the application. If specified, this query MUST be an SQL SELECT statement that returns at least one row.
Why is the validationQuery element needed? When a database server reboots, or there is a network failure, all the connections in the connection pool are broken and this normally requires a Application Server reboot. However, the Commons DBCP (Database Connection Pool) which is used by the Tomcat application server can validate connections before issuing them by running a simple SQL query, and if a broken connection is detected, a new one is created to replace it. To do this, you will need to set the "validationQuery" option on the database connection pool.
Step 4. Configure the Confluence web application
Edit this file in your Confluence installation: /confluence/WEB-INF/web.xml.
Insert the following element just before near the end of the file:
If you are changing an existing Confluence installation over to using a Tomcat datasource:
Edit the /confluence.cfg.xml file.
Delete any line that contains a property that begins with hibernate.
Insert the following at the start of the section.
Step 5. Restart Tomcat
Run bin/startup.sh or bin/startup.bat to start Tomcat with the new settings.