--- title: "SQL for Confluence datasource configuration" canonical: "https://support.appfire.com/space/SQL/74320247/SQL%20for%20Confluence%20datasource%20configuration" format: markdown --- > Macro (aura-html) > ❌ **Archive** > ❌ > ❌ This page has been replaced by [Configure Application Server-based Data Sources](https://appfire.atlassian.net/wiki/spaces/SQL/pages/74318881). Some of the information is out of date with respect to new releases of the add-on. However, we have kept the page as it has comments and answers that may still be helpful. ### Summary --- ### Confluence standalone installation (Tomcat) Many users install the standard Confluence standalone distribution. This section will discuss 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 **/lib** - this is the directory that has other tomcat jars. If you have an **older version of Confluence** that does not have this directory, look for **/common/lib** instead. #### Tomcat configuration Modify **/conf/server.xml** to add one or more datasource resource elements.  is an example of adding a few datasources for various local and non-local databases. The essential element is something like the following where the **datasource** name is **myDS**: ``` ``` > ✅ **Resource must be within the confluence context tag** > ✅ > ✅ ``` > ✅ ... > ✅ > ✅ ... > ✅ > ✅ ... > ✅ > ✅ > ✅ > ✅ ``` --- ### Database examples The **sql** macro markup would be: **{sql:datasource=myDS| ... }** > Macro (csv) #### Other databases Support for other databases depends on the capabilities provided by the JDBC driver. The [SQL for Confluence](https://appfire.atlassian.net/wiki/spaces/SQL) 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. --- ### WebLogic 9.1 Application Server 1. In the WebLogic console, under Services > JDBC, create a data source (see WebLogic's documentation on how to [Configure JDBC data sources](http://edocs.bea.com/wls/docs91/ConsoleHelp/taskhelp/jdbc/ConfigureDataSources.html) for more information). 2. Take note of the JNDI name you used to create the data source. 3. Point the SQL macro to that JNDI name (**datasource** parameter). --- ### Problem determination Here are some common errors and examples. 1. Double check all the configuration values and that JDBC driver is installed - use the information above 2. Make sure you restarted Confluence after making configuration changes 3. Make sure your database is configured from remote access from the Confluence server with the user and password provided. If you have problems, connect using an independent SQL client from the server to verify access. Consult your database documentation for how to configure remote access and database permissions #### Error - no JDBC driver - Check your driver location. The driver must be installed in a location that is on the classpath of your application server. For standalone installations, that would be /lib. #### Error - database server not found - Check your application server (server.xml) configuration and ensure the DNS host name is valid on the server running confluence #### Error - port - Database may not be listening on the requested port - verify port configuration in server.xml and database #### Error - user authentication - Application server configuration (server.xml) has the wrong password #### Error - validation query - Validation query not supported or incorrect syntax - remove the validation query or ensure it is correct for your database #### Error - user authority - User does not have permission to the database or table - modify your database configuration #### Error - bad server.xml configuration - The resource configuration is **outside **of the confluence context - change your application server configuration (server.xml) to ensure the resource is within the confluence context #### Error - class not found - After upgrading Confluence or your application server, this error can occur if your datasource configuration is out of date. Look for something like **factory="org.apache.commons.dbcp.BasicDataSourceFactory"** in your server.xml. Either remove it or rename it to **factory="org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory"**. Reference is SQL-68. #### Error - **Cannot create PoolableConnectionFactory (Could not create connection to database server. Attempted reconnect 3 times. Giving up.)** - Make sure your database server is accepting connections from the Confluence server TCP address and user is authorized to connect. #### Error - MyDS not found - The datasource names are **case sensitive**, make sure you use exactly the same name as what you have configured! #### Non-standard JDBC drivers If you are using a non-standard JDBC driver for accessing less common databases, there are potential problems with unsupported or non-standard behavior. Experiment on a test instance to ensure it works as expected. Here are some workarounds for problems you might encounter. If you continue to have problems, you will need to debug the code on your installation. 1. Hangs - SQL-86 is an example. Use **multipleResults=false** to disable multiple results sets. 2. Avoid using horizontal **rowOrientation** #### Broken database connections - java.sql.SQLRecoverableException Add a validation query to your configuration. This helps the application server connection pool recover from database connection problems. ``` validationQuery="Select 1" ``` #### Other errors For other errors related to connectivity, google your symptoms and application server combination #### SQL exceptions Consult your database documentation as SQL has some database specific differences 🙁. It is best to validate your SQL outside of Confluence before putting it on a page. Use a database admin tools (pgAdmin for instance), some general SQL client, or various Eclipse database plugins.