Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Atlassian ends
Note
Note

Atlassian has ended support for the data source connections

for external data sources

in Confluence 8.0.

It recommends switching to a direct JDBC connection

The recommendation is to switch from the existing JNDI data source connections and move to a direct JDBC connection. For more information, refer to Configuring a data source connection.

Considering the Confluence 8.x upliftment, the upcoming release of SQL for Confluence app will no longer support profiles based on the JNDI data source connections with Confluence 8.x. The configured Application server defined data source (global data source based ) profiles will have to be converted to connection string profiles. Our team is working on this and will soon release the SQL for Confluence app update and update the documentation.

...

Expand
titleWhat will be the next release version of SQL for Confluence app? Will it be compatible with Confluence 7.x versions?

The upcoming release version is SQL for Confluence 11.x, and it will work seamlessly with Confluence 7.x (Confluence 7.4 to Confluence 7.20) versions, including support for JNDI data source connections external data sources.

Expand
titleWhat version of the SQL for Confluence app will be compatible with Confluence 8.x?

The upcoming release version SQL for Confluence 11.x will be compatible with Confluence 8.x and will drop the support for global data source profiles .

Expand
titleWhy are the global data source based profile configurations failing connection in Confluence 8.x?

With Confluence 8.x release, Atlassian has removed the support for the global JNDI data source connections, and hence the connections are failingbased on the JNDI data source connections.

Expand
titleIf the support for external data sources is removed in Confleunce Confluence 8.x, how do I resolve the Application server defined data source (global data source based profile ) configurations?

To resolve this, you need to manually convert the Application server defined data source (global data source profile ) configurations to a local connection string profile.

To convert the global profiles to local profiles, you have the below options:

Create a new

profile

with the Data source name as None, and provide the connection details.
  • Edit the configured global data source profile, change the Data source name to None and provide the connection details.

  • Create a new local profile and choose the created local profile as the Data source name in the configured global data source profiles

    .

    Our team is working on these changes and will soon release the tutorial.

    ...