Connector Drivers Setup Guide
This article explains how to configure the required driver files and native libraries for connectors during system setup.
Some connectors rely on external components, such as JDBC drivers and native libraries, to communicate with source systems. These components must be placed in the correct directories on both the Application Server and the Bridge Client to establish connectivity.
This configuration is typically performed during the initial system setup. However, additional configuration may be required when installing new connectors that depend on drivers or native libraries not previously configured.
When new connectors are introduced, the required JAR files are included with the release artifacts and must be placed according to the procedure described in this document.
If a specific connector requires additional drivers or native libraries, the requirements are documented in the corresponding connector documentation.
Purpose
Configuring connector drivers ensures that the application can establish communication with external systems that require specific drivers or native libraries.
This setup helps to:
Enable connectivity between the application and supported source systems using JDBC drivers
Provide required native authentication libraries
Ensure connector operations function correctly in both direct deployments and Bridge Client deployments.
Prerequisites
Before configuring connector drivers, ensure the following:
The application and Bridge Client are installed and running.
Required driver files are obtained from the connector package or vendor.
Access to the Application Server and Bridge Client machines is available.
Necessary permissions to copy files into system directories.
For the connector driver setup, access to the following components is required:
Third-party JAR path
Tomcat installation directory
Java installation directory
OvalEdge temporary path
If a connector requires additional drivers or libraries, the details are provided in the corresponding connector documentation.
JDBC Driver Configuration
JDBC driver files (.jar) are required for connectors that communicate with the source system via JDBC.
Application Server/Containerized Placement
All JDBC driver files must be placed in the external JAR directory configured in the application.
The directory location is defined by the property: ovaledge.jarpath in the configuration file: oasis.properties
Steps Involved
Locate the oasis.properties file.
The path is configured under <Tomcat>\bin\setenv.sh
Identify the property: ovaledge.jarpath=<external_jar_directory>
Copy the required JDBC driver .jar files into this directory.
During application startup, OvalEdge dynamically loads all JAR files from this directory.
Restart the application to load the newly added drivers.
Bridge Client Placement
For environments using a Bridge Client, JDBC driver files must also be placed in the Bridge Client library directory: <NIFI>/lib
Restart the Bridge Client after adding the driver files.
Example JDBC Drivers
Some commonly required JDBC drivers include:
RedshiftJDBC42-no-awssdk-1.2.45.1069.jar
vertica-jdbc-11.1.1-0.jar
greenplum-jdbc-5.1.4.jar
MicroStrategy Driver Configuration (MSTR.jar)
Some connectors require additional vendor-specific libraries.
For example, the MicroStrategy connector requires the file: MSTR.jar
Application Server Placement
This file must be placed in the OvalEdge application’s temporary directory, as configured in the system settings.
Steps Involved
Log in to the OvalEdge application using an administrator account.
Navigate to Administration > System Settings.
In the System Settings page:
Select the All tab.
In the Key column, search for ovaledge.temppath.
Note the configured temporary path (for example, /home/ovaledge/temp/).
Copy the file MSTR.jar into the configured temporary directory.
Bridge Client Placement
If a Bridge Client is used, the same file must be placed in the Bridge temporary directory.
Steps Involved
Log in to the OvalEdge application using an administrator account.
Navigate to Administration > System Settings.
In the System Settings page:
Select the All tab.
In the Key column, search for bridge.temppath.
Note the configured temporary path (for example, /home/ovaledge/temp/).
Copy the file MSTR.jar into the configured temporary directory.
Native Library Configuration (DLL / SO Files)
Certain connectors require native libraries to support authentication mechanisms or proprietary drivers.
These libraries have the following extensions:
.dll - Windows
.so - Linux
The required files and their purpose are documented in the connector-specific documentation.
Common Native Libraries
Examples of commonly required files include:
sapjco3.dll - Required for Windows installations.
libsapjco3.so - Required for Linux installations.
ntlmauth.dll - Required for Linux installations.
mssql-jdbc_auth-12.8.1.x64.dll - Required for Windows (64-bit).
mssql-jdbc_auth-12.8.1.x86.dll - Required for Windows (32-bit).
Application Server Placement
On the Application Server, copy the native library files to the Tomcat binary directory.
Examples Locations:
Linux: /opt/tomcat/bin
Windows: C:\Tomcat\bin
Bridge Client Placement
On the Bridge Client machine, copy the native library files to the Java binary directory.
Example Location (Windows): C:\Program Files\Java\jdk-21\bin
Important Notes
Restart the OvalEdge application after adding new driver files.
Restart the Bridge Client after adding driver files on the Bridge machine.
Ensure driver versions are compatible with connector requirements.
Refer to the connector-specific documentation if additional files are required.
When using a Bridge Client, ensure that both the Application Server and Bridge Client have the required libraries.
Troubleshooting
If a connector fails to establish a connection, perform the following checks:
Confirm that JDBC driver files are placed in the directory specified by ovaledge.jarpath.
Verify that native library files (.dll/.so) are located in the appropriate bin directories.
Ensure the correct driver versions are used.
Check that the application has sufficient permissions to access the files.
Restart the Application Server and Bridge Client after making changes.
Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?