Task 4.7 Configure Third-party JDBC Drivers for Use with File-AID/EX Execution Server

You can configure a third-party JDBC driver to use with File-AID/EX. Some third-party JDBC drivers will work with File-AID/EX, but they are not supported by BMC. This example is based on a Microsoft-provided MS SQL Server driver, which is considered a third-party driver to File-AID/EX.

Task 4.7.1 Configure the Driver

1. From the Homebase Tools menu, select execution server. Click Stop to stop the execution server.

2. Put the JDBC driver files for the database to be used in the File-AID/EX drivers subdirectory. 

   Tip

   The driver might consist of one or more .jar files or a single .zip file. For example, a Microsoft SQL Server driver consists of three files named: Msbase.jar, Mssqlserver.jar, and Msutil.jar.

3. Perform one of the following steps:

   • To run as a batch job, edit the BatchEngine.bat file (located in the Dme subdirectory). Locate the parameter FAEX_CLASSPATH at the top of the file. Using a semicolon delimiter, add the names of the driver files from Step 2 and save your changes.

     Example

     SET FAEX_CLASSPATH=sumatra.jar
     to:
     SET FAEX_CLASSPATH=sumatra.jar;Msbase.jar;Mssqlserver.jar;Msutil.jar

   • To run via the GUI, define the driver CLASSPATH by inserting the path and name of the driver .jar file at the front of the Windows System CLASSPATH environment variable.

4. Edit the engineJDBC.properties file (located by default at \ProgramData\BMC\FAEX\Cfg and register the driver by appending it using proper syntax. For example, the syntax for driver string “com.microsoft.jdbc.sqlserver.SQLServerDriver” is obtained by unzipping the Mssqlserver.jar file and locating the embedded SqlserverDriver.class file. The class file path is displayed as,
   com\microsoft\jdbc\sqlserver\
   
   The driver string is created by changing the backslash(\) characters to periods (.) and adding the class filename
   

   Important

   The driver string is case-sensitive.

5. Within ConverterPro, use the Connector Type “JDBC Connect String” and enter the proper JDBC URL for the driver of the particular database being accessed.

   Example

   jdbc:microsoft:sqlserver://<server_name>:<port_number>;DATABASENAME=<database_name>

   Important

   The URL is case-sensitive.

Examples

The following list is a compilation of cases were File-AID/EX has successfully connected to the unsupported databases using a third party JDBC driver.

Teradata

Connection String

See connect string from Teradata driver.

DB2 on AS400

Connection String

INFORMIX

Connection String

Register the Driver for usage within File-AID/EX

Add the following line to the engineJDBC.properties file:

.jar Files that Make Up the Driver

ifxjdbc.jar ifxjdbcx.jar

Intersystems Caché

Connection String

User ID: _SYSTEM

Password: sys

Register the Driver for usage within File-AID/EX

Add the following line to the engineJDBC.properties file:

.jar file

Add to the CLASSPATH system variable

Simba Cassandra JDBC

Add the following files to the drivers folder under Workbench install location:

• CassandraJDBC4.jar
• SimbaCassandraJDBCDriver.lic

Connection String

jdbc:cassandra://<server>:<port>;AuthMech=1
The default port is 9042.