This documentation supports the 11.1 version of BMC Discovery.

To view an earlier version of the product, select the version from the Product version menu.

Uploading new JDBC drivers

A JDBC driver is shipped in the form of a single file with an extension of .jar (Java ARchive). The JAR file contains a compiled Java implementation of the client code to remotely talk to the database. Database vendors usually make their JDBC drivers available for free download from their websites.

Due to licensing issues, we cannot ship the drivers for all of the databases that we support. They are available from the vendors' websites for download. We supply the URLs to access these jar files on the JDBC Drivers page. To access this page, from the main menu, click the Administration iconThe Administration page opens. In the Appliance section, click JDBC Drivers.

After you have downloaded the JDBC driver for the database you want to communicate with, upload it to the appliance using the correct Upload link in the table. The file is uploaded and verified. If the required Java class is not found in the jar, or if the jar is corrupt (or not a jar at all) an appropriate message is displayed in the Status column. Simply re-upload the correct driver to correct the issue.

tideway service restart required

You must restart the tideway services before using the newly uploaded JDBC driver.

The available statuses for the drivers are as follows:

  • No JAR Uploaded.
  • Jar Uploaded (Deactivated).
  • Activated and in use—The driver is being used by an SQL credential.
  • Activated but not in use.
  • Error.

BMC Discovery is shipped with a default set of properties files that define the databases you can connect to. If you want to connect to a different database, you must write a properties file and download an appropriate driver. For more information, see Adding new JDBC drivers.

Was this page helpful? Yes No Submitting... Thank you