Using JDBC Driver URLs
A JDBC_DRIVER_DOWNLOAD_URL is an environment variable that specifies URL or a physical location from where container will download/load the driver jars required to make a JDBC connection with the database. If loading the driver from a physical location make sure the location is mounted inside the mount point '/opt/app/tmp' of the container.
Note
Ensure the location from which these URLs are retrieved while processing a job is accessible from the machine where the container is deployed.
Its value consists of comma-separated key-value pairs formatted as:
<Key Name>=<url>Specify unauthenticated URLS only. Authenticated URLs are not supported.
Note
You can provide URLs for multiple databases simultaneously, formatted like this:
<Key Name1>=<url1>,<Key Name2>=<url2><Key Name>=<Mounted Path>For specifying location to load the JDBC driver, you first need to mount the location of driver at host machine to the container's location (
/opt/app/tmp/) when starting the container. Refer to quick start for details.
The following table lists the mapping of supported databases and their respective KeyName.
| Database Name | Key Name |
|---|---|
| Oracle | ORACLE |
| Microsoft SQL Server | MSSQL |
| MySQL | MYSQL |
| PostgreSQL | POSTGRESQL |
| IBM Db2 | DB2 |
| SAP HANA | SAPHANA |
Note
Key Name is case sensitive.
If the JDBC_DRIVER_DOWNLOAD_URL value is not specified during deployment, BDT will use the following default URLs.
Note
When default drivers are used, the MSSQL and MYSQL drivers establish the JDBC connection over SSL.
