Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Teams
, (opens new window)

Simple Issue Language™
Results will update as you type.
  • What's new in SIL®
  • Philosophy behind SIL™
  • Getting started
  • How it works
  • Configuring and installing guide
    • SIL™ configuration
    • SQL data sources
      • Configuring datasources
      • Connecting to remote databases with Power Scripts for Jira cloud
      • JNDI datasource configuration
      • CSV files data
    • Mail configuration
    • Asynchronous runner
    • Remote systems
    • LDAP configuration
    • Script storage
    • Custom Field Mappings
    • Configure Jira logging
    • SMS Sender configuration
    • Webhooks configuration
    • Integration with Stride and Slack
  • Simple Issue Language™ usage
  • SIL™ Template language
  • Tools and utilities
  • Development using SIL
  • Common REST service
  • How-to articles
    Calendars
You‘re viewing this with anonymous access, so some content might be blocked.
/
Configuring datasources

Configuring datasources

Oct 22, 2021

Looking for the documentation on the newest versions of SIL Engine and the Simple Issue Language for Jira 8 for Server/Data Center? Click here !

Adding a Datasource

To create a data source from the user interface, access the Datasources menu in cPrime Add-ons section, then click Add Datasource.

Fill out the necessary fields:

  1. Name of the datasource, identifying uniquely ( * ) your data source
  2. The database type
  3. The JDBC URL, with the syntax the driver understands
  4. Username and password for the database, if applicable

Optionally, you may control the pool parameters:

  • Validation query - The SQL query that will be used to validate connections from the pool.
  • Initial size - Number of initial connections.
  • Max Active - Maximum number of active connections that can be allocated at the same time.
  • Max Idle - The maximum number of connections that can remain idle in the pool.
  • Min Idle - The minimal number of connections that can remain idle in the pool.

These are DBCP parameters that are used when defining any JNDI datasource. Once you have configured your datasource, you are ready to test it. Any error is picked up and shown in this dialog so you can review the parameters, make the changes and test again. When it works, just save it, your new datasource is ready to be used.

Important (*)

The identification of the datasource is unique only among these ones, defined in the Kepler suite. As we explained, the name here takes precedence over any JNDI name that happens to be the same.

Very Important!

JDBC Driver must be already loaded (for instance placed in Jira's lib folder).


At the moment, there's no possibility to monitor the performance of the SQL pool, so you will have to rely on external tools, specific to your database / operating system.

Managing Datasources

The datasources screen lists all your datasources and allows to edit, test and remove operations to be performed on each datasource. Note that there's no warning when removing a datasource that is in use by your SIL™ programs, so take care when performing destructive operations. Changes in the datasources are picked up immediately.

See also

  • JNDI datasource configuration
  • CSV files data
, multiple selections available,
{"serverDuration": 14, "requestCorrelationId": "0038d11d920a4724b5557b948af16452"}