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 Next »

Download the Java .jar library

Download the driver above and install it on your Java tool as usual.

JDBC connect string

Then configure a connection to the SQL Cloud database:

  • URL: jdbc:jira-cloud:<port> (a random port)

  • Username: Must match the name of the Jira instance (https:<instance>.atlassian.net>)

  • Password: Must match the password on SQL Cloud - Query Server page (https://<instance>.atlassian.net/plugins/servlet/ac/expert.marketplace.jira.cloud.sql/sqlc-server)

Prerequisites

  • Minimum Java version 1.8

  • For Java +17 these JVM parameters must be added to the command line:

--add-opens java.base/java.lang=ALL-UNNAMED

--add-opens java.base/java.math=ALL-UNNAMED

--add-opens java.base/java.util=ALL-UNNAMED

--add-opens java.base/java.util.concurrent=ALL-UNNAMED

--add-opens java.base/java.net=ALL-UNNAMED

--add-opens java.base/java.text=ALL-UNNAMED

How it works?

SQL Cloud is a 100% JavaScript database. Therefore a browser page is always required to run the database. This is a Jira page, hence the user must be logged in Jira to view the page and connect to.

This may look weird, but the JDBC Driver cares about this process as it is capable to automatically open a page on your favorite browser when it is required, run the database on it and connect to. There is no user’s action required.

Of course, that page is provided by the SQL Cloud app:

Every time that a Java tools opens a database connection against Jira Cloud a new instance of the page above will be automatically opened on the local machine running the JDBC Drive.

The page displays the database connection status on it:

The connection limit to connect is 10 seconds. After that threshold a timeout exception will be raised.

The database username is the Jira instance name in URL page.

The database password can be read from that page. Initially a random password is created, but the user can change it or create a new one automatically by saving it blank.

The database port does not matter. You can use any one available in the local machine and the JDBC Driver will use it for all the local communication. This is also set in the JDBC connection URL.

  • No labels