.png?version=1&modificationDate=1662627367996&cacheVersion=1&api=v2&width=226&height=72)
On this page
Description
Data Source Profiles allow the Confluence Administrator to extend Data Sources by providing additional configuration parameters for use by SQL macros. Like Data Sources, Data Source Profiles are referenced by the SQL, SQL-query, and SQL-file Macros using the dataSource parameter.
Note: you must have at least one Data Source in order to begin using this application within Confluence.
Add Data Source Profiles
To add new or extend an existing Data Source Profile:
- Log in as a user with the Confluence Administrators Global Permission.
- Select Add-ons from the Administration menu (cog icon:
) at the top right of your screen. Then scroll down to Bob Swift Configuration on the left-hand nav bar and choose SQL Configuration (see: 
). - Select View and Modify Data Source Profiles (see:
) from the top navigation. - Click on the
button.
The Add Profile screen will provide you with two setup options:
- Simple - this is the most straightforward way to connect to your database.
- By connection string - use this option if you want to specify additional parameters and are comfortable constructing a database URL.
Depending on the setup type, you'll be prompted for the following information.
| Setup type | Field | Description |
|---|---|---|
| Simple | Database type | They type of database you are connecting to. |
| Simple | Data source name | You have the option to create a new Data Source Profile by extending an existing Data Source. This may be useful if you'd like to tighten/alter the configuration parameter settings to be more/less restrictive for certain usage. You can of course then secure the usage using our Macro Security for Confluence App. |
| Simple | Hostname | This is the hostname or IP address of your database server. |
| Simple | Port | This is the port used to access your database on the server it is running against. |
| Simple | Database | This is the name of your database. |
| Both | Driver class | The class of JDBC driver that you will use to connect to your database (e.g., com.mysql.jdbc.Driver, or org.postgresql.Driver) |
| Both | Driver JAR location | The path on your Confluence server where the JDBC driver is located. Start with an absolute file reference Usually better to start with an absolute reference to make sure it is working. Relative references are more maintainable, but can be problematic especially on Windows. After it is working, you can experiment with relative references. |
| By connection string | Connection string | The database URL is entered in this format (SQLServer example):jdbc:sqlserver://<hostname>:<port>;database=<database> For example: |
| Both | Username | This is the username of your dedicated database user. |
| Both | Password | This is the password for your dedicated database user. |
Extended Parameters
Data Source Profiles allow for the configuration of extended parameter options. These profile-wide settings will be used by all SQL Macros if not overridden at the Macro-level.
Table: extended parameter options explained
| Parameter | Macro Parameter | Default | Description |
|---|---|---|---|
| Limit rows processed | limit | No limit | The maximum number of rows that will be processed and displayed by SQL macros. This prevents queries that result in a large number of rows from using excessive resources. Individual queries can use the limit parameter to override this value. The following options are available for selection:
|
| Limit query time | queryTimeout | None | The number of seconds that a query can take before we force a timeout. This prevents queries that take too long from impacting other users. Individual queries can use the queryTimeout parameter to override this value. Note, this parameter:
|
| Limit max active | maxActive | Noone | Used to limit the number of actively executing SQL queries for a specific data source. Once the maximum active limit is reached, the next requested render of a sql macro using the specific data source will return an error message instead of trying to connect to the database. See this article for additional information. |
| Show sql options | showSqlOptions | None | Since 6.4. A comma separated list of code or code-pro (Code Pro Macro) parameters used when Show SQL is selected. This allows for customization of how the SQL code is shown. See How to improve the display of SQL source. |
| Connection properties | connectionProperties | None | A list of driver specific properties passed to the driver for creating connections. Each property is given as name=value, multiple properties are separated by semicolons (;). See Apache Tomcat JNDI resources. |
| Initial SQLs | initalSql<n> | None | SQL that is run after the SQL connection is established where n is a number (1, 2, 3, ...). Multiple initial SQL statements are allowed to support databases that only allow single SQL statements. Example use for Oracle: initialSql1=ALTER SESSION SET NLS_TERRITORY = GERMANY|initialSql2=ALTER SESSION SET NLS_LANGUAGE = GERMAN No results are kept and any errors will generate a macro exception. Using beforeSql is recommended for Postgres and other database that support multiple sql statements as it is more efficient than multiple separated actions. |
| Before SQL | beforeSql | None | SQL that is added before Macro defined SQL. |
| After SQL | afterSql | None | SQL that is added after Macro defined SQL. |
View Data Source Profiles
To view, add, or modify a Data Source Profile:
- Log in as a user with the Confluence Administrators Global Permission.
- Select Add-ons from the Administration menu (cog icon: ) at the top right of your screen. Then scroll down to Bob Swift Configuration on the left-hand nav bar and choose SQL Configuration (see: ).
- Select View and Modify Data Source Profiles (see: ) from the top navigation.
- You will see a list of Data Source Profiles and their connection status.
Note: The connection status 
indicates that the connection information supplied for the Data Source Profile will allow connections from Confluence to the targeted database. This does not indicate that the Data Source Profile is in use by any Macros on Confluence pages.
Security
Data sources are shared resources. Some of these resources may need to be secured for use only by specific users or groups. This can be accomplished by using Macro Security for Confluence and configuring access to the macro and perhaps to individual profiles.
Copy and paste the configuration into your data source profile configurationQuick Configurations
- Change the name to something meaningful for your organization
- Modify the url to your database server
- Modify the database name (from test to the name of database you want to query)
- Modify the user and password to be match the user credentials defined for the the database server
To test: create a page and use Insert -> Markup to add the following wiki markup : {sql-query:dataSource=example} select 1 {sql-query}
dataSource not found
All 5 db parameters are required when defining db access directly. Otherwise you will likely get a dataSource not found message.
Using the lib location
Often, using the lib location (example: dbJar=lib/ojdbc6.jar) is best especially if you already have or later intend to define an application server based data source. The following is for a standalone installation.
