Skip to end of banner
Go to start of banner

Configure Data Sources

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Current »

Overview

(info) At least one Data Source or Data Source Profile needs to be configured before you can use the SQL Macro or SQL-query Macro or SQL-file.

This page describes two methods to configure Data Sources for the macros provided by SQL for Confluence. SQL Macros use Data Sources to access databases. A Data Source defines the access parameters including credentials. The same database access information is required for each method. Similarly, the database must allow access using the information provided no matter which method is used.

MethodPrimary BenefitKey AttributesDocumentationExpress EditionPro Edition
Data Source ProfilesConvenience
  • SQL for Confluence specific configuration
  • Convenience 
    • Configuration change in affect immediately
    • File system access not needed
  • Can reference application server defined Data Sources
  • Recommended for evaluation, testing, short term scenarios
  • Medium or heavier use scenarios should also employ Cache for Confluence
Configure Data Source Profiles(tick)(tick)
Application Server-based Data SourcePerformance
  • Application server based configuration
  • Best performance via connection pooling/reuse
  • Requires Confluence restart after configuration change
  • Recommended for long term/heavy use scenarios
Configure Application Server-based Data Sources - v9(error)(tick)

You can configure data sources using either of the methods or both - for instance use a data source profile while testing or for low-use scenarios, then switch to a server-based data source when/if it becomes clear it is going to be around for a long while.

Macro Security for data source access control

Macro Security for Confluence can be used to control access to specific Data Sources in the same way no matter what method is used.

Use Cache and Future macros around SQL macros

Give your users better response times and reduce the load on your server by using Cache for Confluence macros for heavy use scenarios.

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. The configuration must be done by a Confluence administrator and the Confluence application server must be restarted for changes to be active. The configuration must be done very carefully as any errors result in the Data Source being unusable (sad). Each database you need to access in Confluence needs to a have a Data Source configuration.

Configure Application Server-based Data Sources - v9

  • No labels

Log a request with our support team.

Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.

Error formatting macro: appfire-confluence-analytics: java.lang.NullPointerException: Cannot invoke "com.atlassian.confluence.xhtml.api.MacroDefinition.getMacroId()" because "macroDefinition" is null