Generic Connections

Generic database connections

Connecting to databases not mentioned in the Wizard

You can set up a direct connection to many types/brands of database which the Database Connection dialogue does not explicitly support. Providing your database vendor offers a JDBC driver or ODBC connectivity, you should be able to use this to allow Omniscope to connect directly to your database.

Generic JDBC connections

For best results, find a JDBC driver for your database. The vendor should provide this.  Usually, the latest version of the JDBC driver is best even for older versions of databases, but if you run into problems, match the versions.
You will need:
  1. The path to the JDBC driver JAR file (this may come as part of an installation package, or as a JAR file download).  You should be able to download this from the database vendor.
  2. The "driver class name", which is a fixed value such as "com.vendor.product.Driver". For example, the Oracle driver class name is "oracle.jdbc.OracleDriver". This should be provided in the JDBC driver's accompanying documentation.
  3. The "JDBC URL" which is specific to the type of database and your database instance, and might look like "jdbc:product/myhostname/mydatabasename". For example, the Oracle JDBC URL looks like "jdbc:oracle:thin:@hostname:1521:orcl".  This also should be described in the JDBC driver's accompanying documentation.
Enter/configure this in the Omniscope database dialogue JDBC page, then proceed through as for other database types, selecting the table and optionally customising the SQL.

ODBC

If you cannot get this to work, try the ODBC approach.  You will need to know how to set up a named ODBC data source in Windows that connects to your database.  When you have this set up, enter the data source name (you will have chosen this when you set up the ODBC data source) into the Omniscope database dialogue's ODBC option.
 
Feedback

If you are unable to get this to work, please post the problem on the forums

If you are successful, please let us know what the settings were and where you obtained the JDBC driver from, so we can update our KnowledgeBase and consider adding explicit support for your database vendor to Omniscope.