.png?version=1&modificationDate=1662627367996&cacheVersion=1&api=v2&width=226&height=72)
On this page
The SQL for Confluence (Pro Edition) app version 11.x has removed the support for application server-defined data sources in Confluence 8.x. (Atlassian has ended support for the data source connections in Confluence 8.0. For more information, refer to Configuring a data source connection.)
In Confluence 8.x, we recommend reconfiguring the application server-defined data source profile to the connection string profile. For more information, refer to How to convert an application server defined data source profile to a connection string profile.
SQL for Confluence (Pro Edition) app version 11.x works seamlessly with Confluence 7.x (Confluence 7.4 to Confluence 7.20) versions, including support for application server-defined data sources (JNDI data source connections).
Summary
This Getting Started - Configuration page provides instructions for configuring the Appfire Atlassian app - SQL for Confluence version 11.0. It also lists the various configuration options with a detailed description, so that you can customize your app using the available options.
Configure SQL for Confluence
After upgrading or installing SQL for Confluence, follow the steps mentioned below to navigate to the Global configuration:
- Log in as a user with the system administrator's Global Permission.
- Select CONFLUENCE ADMINISTRATION > Manage apps from the Administration menu (cog icon:
) at the top right of your screen. Then scroll down to BOB SWIFT CONFIGURATION on the navigation bar to the left and choose SQL (Pro Edition).
(See:
)
Global Configuration
This configuration page contains global settings that will control the behavior of data sources and data source profiles. Once saved, settings chosen on this page is applied to all macros across pages.
Table: configuration options explained
| Option | Default | Description |
|---|---|---|
| Limit rows processed | No limit | The maximum number of rows to be processed and displayed by SQL macros. This prevents queries that use excessive resources resulting in a large number of rows. Individual queries can use the limit parameter to override this value. The following options are available from a selection list:
|
| Limit query time | No limit | The number of seconds that a query can take before a forced timeout. This prevents queries that take too long, from impacting other users. Individual users can use the queryTimeout parameter to override this value. The following options are available from a selection list:
Note, this parameter:
|
| Transaction isolation level | Read committed | Default level used if the macro parameter does not specify a specific level. The following options are available for selection:
Note this parameter requires that the target database and JDBC driver support transaction isolation levels. |
| Disable anti-XSS mode | Off | Anti-XSS mode reduces exposure to XSS exploits related to SQL app macros. By default, the app respects Confluence's global Anti-XSS settings. This configuration allows an administrator to globally turn off anti-XSS mode only for the SQL Macro. An alternative method is to enable groups or individuals from using the disableAntiXss parameter to control this for individual Macros. This may be necessary for queries that require producing HTML constructs. Note that disableAntiXss parameter use can be controlled by the Macro Security for Confluence app. |
| Help us improve the product | ON | Enable this option to report usage data that helps us to improve the app continually. The app does not send any private user data or personally identifiable information. To learn more about what is shared, refer to Analytics data. |
