Copying a CData JAR File Installed Locally to a Remote Server
To be able to import data into Sisense via connectors, you need to download and deploy the connector’s JAR file on the machine from where your are accessing Sisense. However, if you are accessing Sisense on a remote server, working directly on the server might not be convenient or even impossible.
In this case, you can download and deploy the driver on your local machine (or any other machine, as convenient), perform all the authentication on that machine, and then copy only the JAR file to the remote server. Sisense recommends this type of deployment in cases of Linux deployment and when working on Sisense Managed Cloud Service.
Note: The process is compatible with Windows and Linux servers. However, if you are on Linux deployment, you must work in this remote location: /opt/sisense/storage/
To copy a JAR file installed locally to a remote server:
- Download the driver on your local machine or any other machine, as convenient. For details, see Downloading the JDBC Driver for Your Application.
- Deploy the driver on your local machine. For details, see Connecting to JDBC.
- Obtain a connection string from the Connection String Builder dialog and perform a Test Connection on your local machine. For details, see Connecting to Your Application via a Connection String.
- Create a new folder inside the directory C:\ProgramData\Sisense\DataConnectors\jdbcdrivers. Name the folder by the name of your driver. For example, for the Box driver, name the folder 'Box'.
- Once the connection is successful, copy the JAR file into the folder that you created.
- Open Sisense. In the Connection String field, paste the generated connection string. In the JDBC JARs Folder, enter the name of the folder that your created. In Driver's Class Name, enter the driver class name. Then click Next. For details, see Importing Your Application’s Tables into Your ElastiCube.
Note: If an OAuth JWT or SSL certificate (e.g. SSLServerCert or SSLClientCert) is being used on the remote server, append the location of these files on the server to the connection string. Do that only if the location where these files reside on the remote server is different from their location on the machine where you installed the driver.