Installing and Maintaining Custom JDBC Drivers

Installation of Topaz Enterprise Data creates and initially populates the 'drivers' directory in Topaz Workbench installation location. It contains a set of several JDBC drivers providing connectivity to SQL Server, Sybase, Derby, Access, and Excel. If the user performing the installation accepts the Oracle License Agreement, an Oracle JDBC driver is also installed in the same directory. Refer to Enable DB2 JDBC Repository and Database Access Support for the steps for adding the IBM DB2 JDBC driver support.

Still, a user may want to install additional JDBC drivers for other databases, such as Teradata or MySQL, or to use a different version of these already installed drivers. Also, if a user works with multiple installations of Topaz Enterprise Data, keeping the modified sets of drivers consistent between different installations can be cumbersome.

Topaz Enterprise Data allows users to install such custom JDBC drivers into any directory. In that case, the user needs to create an environment variable "TOPAZ_DRIVERS" pointing to the JDBC drivers location, restart the communication manager and the Local execution server (refer to Shutting Down or Restarting Local Execution Server and Local Communication Manager ) and all these drivers will be available for Topaz Enterprise Data applications.

Note: See the task Configure the Driver for details on additional steps that may be required to make the newly added drivers usable.

Note: If different versions of the same driver are installed both at <Topaz Installation directory>\Drivers and %TOPAZ_DRIVERS% locations, the first takes precedence.