Datasources configuration


Table of contents



Datasources configuration page

Elements Connect datasources definitions can be configured from Connect administration page, in the "Datasource" section:






Preconfigured Jira datasources

On a fresh install of Elements Connect, 3 datasources are preconfigured

  • Jira Issues (JQL)
  • Jira database (SQL)
  • Jira REST API

They cannot be deleted.

Learn more about preconfigured Jira datasources.



Preconfigured application link datasources

If the Jira instance is linked with others Atlassian applications (Confluence, Bamboo, Jira, ...) through an application link, those applications will be available as datasources.

They cannot be deleted.

Learn more about preconfigured application datasources.



Create a new datasource definition

Datasources definitions can be created using the "Create a datasource" button.





Elements Connect supports various datasource types:

Database

Through a direct connection using the "Database" type.

Learn more about database datasource definition configuration

JNDI reference

Using a JNDI reference configured in Tomcat.

Learn more about JNDI datasource definition configuration

URL

Commonly used to connect an Elements Connect field to a REST API.

Learn more about URL datasource definition configuration

LDAP

Use this datasource to connect an Elements Connect field to a user directory using the Lightweight Directory Access Protocol.

Learn more about LDAP datasource definition configuration

File

Use this datasource to connect an Elements Connect field to a file. 
CSV, XML and JSON file formats are supported.

Learn more about file datasource definition configuration

Salesforce

Use this datasource to connect an Elements Connect field to Salesforce "search" API.

Learn more about Salesforce datasource definition configuration



Datasources status

Datasources have two different statuses:

  • IN USE - the datasource is used by at least one field configuration and cannot be deleted
  • NOT USED - the datasource is not used by any field configuration and can be deleted