How to connect Salesforce Data Cloud (Data 360) to Tableau

Introduction

You can connect to your Salesforce Data Cloud (Data 360) data from Tableau via the high-performance Salesforce Data Cloud (Data 360) ODBC Driver (powered by ZappySys JDBC-ODBC Bridge Driver). We'll walk you through the entire setup.

Let's not waste time and get started!

Prerequisites

Before we begin, make sure you meet the following prerequisite: Java Runtime Environment (JRE) or Java Development Kit (JDK) must be installed on your system.

• Minimum required version: Java 8
  • Amazon Corretto 8
  • Oracle JRE 8
• Recommended Java version: Java 21
  • Amazon Corretto 21
  • Oracle JRE 21

If your JDBC Driver targets a different Java version (e.g., 11 / 17 / 21), install the corresponding or newer Java version.

Download Salesforce Data Cloud (Data 360) JDBC driver

To connect to Salesforce Data Cloud (Data 360), you will have to download JDBC driver for it, which we will use in later steps. Let's perform these little steps right away:

1. Visit Salesforce Data Cloud (Data 360) website or MVN Repository.

2. Select the appropriate JDBC driver version in Latest Versions section in MVN Repository:

   

3. Download the JDBC driver, and save it locally, e.g. to C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar.

   

4. Done! That was easy, wasn't it? Let's proceed to the next step.

Create data source in ZappySys Data Gateway

In this section we will create a data source for Salesforce Data Cloud (Data 360) in the Data Gateway. Let's follow these steps to accomplish that:

1. Download and install ODBC PowerPack (if you haven't already).

2. Search for gateway in the Windows Start Menu and open ZappySys Data Gateway Configuration:

   

3. Go to the Users tab and follow these steps to add a Data Gateway user:

   • Click the Add button
   • In the Login field enter a username, e.g., john
   • Then enter a Password
   • Check the Is Administrator checkbox
   • Click OK to save
   

4. Now we are ready to add a data source:

   • Click the Add button
   • Give the Data source a name (have it handy for later)
   • Then select Native - ZappySys JDBC Bridge Driver
   • Finally, click OK
   SalesforceDataCloudData360DSN

   ZappySys JDBC Bridge Driver

   

5. Now, we need to configure the JDBC connection in the new ODBC data source. Simply enter the Connection string, credentials, configure other settings, and then click Test Connection button to test the connection:

   SalesforceDataCloudData360DSN

   jdbc:salesforce-datacloud://login.salesforce.com

   com.salesforce.datacloud.jdbc.DataCloudJDBCDriver

   C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar

   optional for Salesforce Data Cloud (Data 360)

   optional for Salesforce Data Cloud (Data 360)

   optional for Salesforce Data Cloud (Data 360)

   

   For Production (login.salesforce.com), use these values when setting parameters:

   • Connection string: jdbc:salesforce-datacloud://login.salesforce.com
   • Driver class: com.salesforce.datacloud.jdbc.DataCloudJDBCDriver
   • JDBC driver file(s): C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar
   • User name:
   • Password:
   • Client ID (Consumer Key):
   • Client Secret (Consumer Secret):
   • Data space: default

     Follow these steps to create a Salesforce External Client App (or a legacy Connected App) so the Data Cloud JDBC driver can authenticate. JDBC Bridge then exposes Data Cloud SQL to Power BI, SQL Server Linked Server via ZappySys Data Gateway, Crystal Reports, SSRS, Azure Data Factory, and other ODBC tools.

     WARNING: As of 21 Feb 2026 Salesforce no longer lets you create new Connected Apps. Use an External Client App. If you already have a Connected App, you can keep using it with username/password + consumer key/secret. Do not use a personal employee login for unattended jobs (Power BI refresh, Linked Server, ADF). Use a dedicated integration user.
     1. Sign in to Salesforce Setup as an administrator.
     2. Go to App Manager (or External Client Apps) and create a new External Client App / Connected App. Enable OAuth Settings.

     3. Callback URL (Redirect URI) must be exactly:

        https://zappysys.com/oauth

        INFO: Use this ZappySys capture page so the authorization code appears in the page title and URL during the 3-legged dance. Do not use localhost, a Salesforce "try it" page, or any other URL -- those often redirect again or drop the query string, so the code is not visible.
     4. Select OAuth scopes your org requires for Data Cloud query (typically includes Data Cloud / CDP query and API access). Save.
     5. Open Manage Consumer Details and copy Consumer Key (Client ID) and Consumer Secret (Client Secret).
     6. Paste username, password (plus security token if your org requires it), Client ID, and Client Secret into this Auth profile.
     7. If you complete a browser authorization, wait until the browser lands on https://zappysys.com/oauth and the code is in the title or address bar.
     8. Finish the wizard. Then click Test Connection on the DSN Main UI (the wizard does not run Test Connection).
     9. Done. You can query from C#, Python, PowerShell, and ODBC apps.

   For Sandbox (test.salesforce.com), use these values when setting parameters:

   • Connection string: jdbc:salesforce-datacloud://test.salesforce.com
   • Driver class: com.salesforce.datacloud.jdbc.DataCloudJDBCDriver
   • JDBC driver file(s): C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar
   • User name:
   • Password:
   • Client ID (Consumer Key):
   • Client Secret (Consumer Secret):
   • Data space: default

     Follow these steps to create a Salesforce External Client App (or a legacy Connected App) so the Data Cloud JDBC driver can authenticate. JDBC Bridge then exposes Data Cloud SQL to Power BI, SQL Server Linked Server via ZappySys Data Gateway, Crystal Reports, SSRS, Azure Data Factory, and other ODBC tools.

     WARNING: As of 21 Feb 2026 Salesforce no longer lets you create new Connected Apps. Use an External Client App. If you already have a Connected App, you can keep using it with username/password + consumer key/secret. Do not use a personal employee login for unattended jobs (Power BI refresh, Linked Server, ADF). Use a dedicated integration user.
     1. Sign in to Salesforce Setup as an administrator.
     2. Go to App Manager (or External Client Apps) and create a new External Client App / Connected App. Enable OAuth Settings.

     3. Callback URL (Redirect URI) must be exactly:

        https://zappysys.com/oauth

        INFO: Use this ZappySys capture page so the authorization code appears in the page title and URL during the 3-legged dance. Do not use localhost, a Salesforce "try it" page, or any other URL -- those often redirect again or drop the query string, so the code is not visible.
     4. Select OAuth scopes your org requires for Data Cloud query (typically includes Data Cloud / CDP query and API access). Save.
     5. Open Manage Consumer Details and copy Consumer Key (Client ID) and Consumer Secret (Client Secret).
     6. Paste username, password (plus security token if your org requires it), Client ID, and Client Secret into this Auth profile.
     7. If you complete a browser authorization, wait until the browser lands on https://zappysys.com/oauth and the code is in the title or address bar.
     8. Finish the wizard. Then click Test Connection on the DSN Main UI (the wizard does not run Test Connection).
     9. Done. You can query from C#, Python, PowerShell, and ODBC apps.

   For JWT Bearer (External Client App), use these values when setting parameters:

   • Connection string: jdbc:salesforce-datacloud://login.salesforce.com
   • Driver class: com.salesforce.datacloud.jdbc.DataCloudJDBCDriver
   • JDBC driver file(s): C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar
   • User name:
   • Client ID (Consumer Key):
   • Private key (PEM):
   • Data space: default

     JWT Bearer Flow with an External Client App (current Salesforce recommendation for JDBC). No refresh-token dance; you still register the callback URL so the app is valid.

     1. Create an External Client App in Salesforce Setup. Enable OAuth and JWT Bearer.
     2. Callback URL must be exactly https://zappysys.com/oauth (do not use localhost or another capture URL).
     3. Upload or generate a certificate. Download the private key as PEM (-----BEGIN PRIVATE KEY-----).
     4. Copy the Consumer Key (Client ID).
     5. Paste Client ID, integration username, and the full PEM into this profile. Do not check a private key into source control.
     6. Finish the wizard. Then click Test Connection on the DSN Main UI (the wizard does not run Test Connection).
     7. Done. You can query from C#, Python, PowerShell, and ODBC apps.

6. You should see a message saying that connection test is successful:

   

7. Otherwise, if you are getting an error, start by troubleshooting the JDBC connection with DBeaver in the section below:

   Jump to troubleshooter

8. We are at the point where we can preview a SQL query. For more SQL query examples visit JDBC Bridge documentation:

   SalesforceDataCloudData360DSN

   SHOW TABLES

   

   SHOW TABLES

   You can also click on the <Select Table> dropdown and select a table from the list.

   The ZappySys JDBC Bridge Driver acts as a transparent intermediary, passing SQL queries directly to the JDBC driver, which then handles the query execution. This means the JDBC-ODBC Bridge Driver simply relays the SQL query without altering it.

   Some JDBC drivers don't support INSERT/UPDATE/DELETE statements, so you may get an error saying "action is not supported" or a similar one. Please, be aware, this is not the limitation of ZappySys JDBC Bridge Driver, but is a limitation of the specific JDBC driver you are using.

9. Click OK to finish creating the data source.

10. Once done, go to the Network Settings tab and Add a firewall rule for inbound traffic:

    
    • This will initially allow all inbound traffic.
    • Click Edit IP filters to restrict access to specific IP addresses or ranges.

11. Crucial Step: After creating or modifying the data source, you must:

    • Click the Save button to persist your changes.
    • Hit Yes when prompted to restart the Data Gateway service.

    This ensures all changes are properly applied:

    
    Skipping this step may cause the new settings to fail, preventing you from connecting to the data source.

Read data in SQL Server via Data Gateway

After configuring your data source using the ZappySys ODBC Driver, the next mandatory step to read that data in SQL Server is to create a Linked Server. SQL Server requires a Linked Server definition to access any ODBC-based source through the ZappySys Data Gateway, allowing the source driver data to be queried using standard T-SQL.

• Method 1: Using a SQL Script automatically generated by the Data Gateway
• Method 2: Using SQL Server UI (SSMS) to manually configure the Linked Server

Method 1: Using a SQL Script automatically generated by the Data Gateway

The fastest and most reliable way to create the Linked Server is to use the SQL Script generated by the Data Gateway. This ensures all settings are applied correctly with minimal manual steps.

1. In the Data Gateway, open the App Integration tab.

2. Update the prefilled Linked Server Name if you want to use a custom name.

3. Select the SalesforceDataCloudData360DSN data source which we created earlier as the Database.

4. Choose the correct SQL Server version for your environment.

   • SQL 2019 or Lower (@provider='SQLNCLI11')
   • SQL 2022 or Higher (@provider='MSOLEDBSQL')

5. Click Generate Code.

6. In the generated script scroll down to 4. Attach Gateway login with linked server step, enter your Data Gateway admin username and password.

   'LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY'

   

7. Press Ctrl + A and Ctrl + C to copy the entire script.

   LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY

   SalesforceDataCloudData360DSN

   

8. Paste the script into SQL Server Management Studio (SSMS) and run it.

   

9. That's it linked server is created in the SQL Server.

10. Finally, open a new query and execute a query we saved in one of the previous steps:
    

    SELECT * FROM OPENQUERY([LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY], 'SHOW TABLES')

    

    SELECT * FROM OPENQUERY([LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY], 'SHOW TABLES')

Sample SQL Script for Creating a Linked Server in SQL Server

USE [master]
GO
--///////////////////////////////////////////////////////////////////////////////////////
--Run below code in SSMS to create Linked Server and use ZappySys Drivers in SQL Server
--///////////////////////////////////////////////////////////////////////////////////////

-- Replace YOUR_GATEWAY_USER, YOUR_GATEWAY_PASSWORD
-- Replace localhost with IP/Machine name if ZappySys Gateway Running on different machine other than SQL Server
-- Replace Port 5000 if you configured gateway on a different port


--1. Configure your gateway service as per this article https://zappysys.com/links?id=10036

--2. Make sure you have SQL Server Installed. You can download FREE SQL Server Express Edition from here if you dont want to buy Paid version https://www.microsoft.com/en-us/sql-server/sql-server-editions-express

--Uncomment below if you like to drop linked server if it already exists
--EXEC master.dbo.sp_dropserver @server=N'LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY', @droplogins='droplogins'

--3. Create new linked server

EXEC master.dbo.sp_addlinkedserver
    @server = N'LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY'  --Linked server name (this will be used in OPENQUERY sql
, @srvproduct=N''
---- For MSSQL 2012, 2014, 2016, 2017, and 2019 use below (SQL Server Native Client 11.0)---
, @provider=N'SQLNCLI11'
---- For MSSQL 2022 or higher use below (Microsoft OLE DB Driver for SQL Server)---
--, @provider=N'MSOLEDBSQL'
, @datasrc=N'localhost,5000' --//Machine / Port where Gateway service is running
, @provstr=N'Network Library=DBMSSOCN;'
, @catalog=N'SalesforceDataCloudData360DSN' --Data source name you gave on Gateway service settings

--4. Attach gateway login with linked server

EXEC master.dbo.sp_addlinkedsrvlogin
@rmtsrvname=N'LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY'  --linked server name
, @useself=N'False'
, @locallogin=NULL
, @rmtuser=N'YOUR_GATEWAY_USER' --enter your Gateway user name
, @rmtpassword='YOUR_GATEWAY_PASSWORD'  --enter your Gateway user's password
GO

--5. Enable RPC OUT (This is Optional - Only needed if you plan to use EXEC(...) AT YourLinkedServerName rather than OPENQUERY
EXEC sp_serveroption 'LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY', 'rpc', true;
EXEC sp_serveroption 'LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY', 'rpc out', true;

--Disable MSDTC - Below needed to support INSERT INTO from EXEC AT statement
EXEC sp_serveroption 'LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY', 'remote proc transaction promotion', false;

--Increase query timeout if query is going to take longer than 10 mins (Default timeout is 600 seconds)
--EXEC sp_serveroption 'LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY', 'query timeout', 1200;
GO

Method 2: Using SQL Server UI (SSMS) to manually configure the Linked Server

You can also create the Linked Server manually through SSMS if you prefer a visual setup. This method lets you configure the provider, data source, and security interactively.

1. First, let's open SQL Server Management Studio, create a new Linked Server, and start configuring it:

   LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY

   Microsoft OLE DB Driver for SQL Server

   localhost,5000

   SalesforceDataCloudData360DSN

   SalesforceDataCloudData360DSN

   
   • For SQL Server 2012, 2014, 2016, 2017, and 2019, choose SQL Server Native Client 11.0 as the provider.
   • For SQL Server 2022 or higher, choose Microsoft OLE DB Driver for SQL Server as the provider.

2. Then click on Security option and configure username we created in ZappySys Data Gateway in one of the previous steps, e.g. john:

   

3. Optional step. Under the Server Options, Enable RPC and RPC Out and Disable Promotion of Distributed Transactions(MSDTC).

   

   You need to enable RPC Out if you plan to use EXEC(...) AT [LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY] rather than OPENQUERY.
   If don't enabled it, you will encounter the Server 'LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY' is not configured for RPC error.

   Query Example:

   DECLARE @MyQuery NVARCHAR(MAX) = 'SHOW TABLES';
   
   EXEC (@MyQuery) AT [LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY];

   ---

   If you plan to use 'INSERT INTO <TABLE> EXEC(...) AT [LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY]' in that case you need to Disable Promotion of Distributed Transactions(MSDTC).
   If don't disabled it, you will encounter the The operation could not be performed because OLE DB provider "SQLNCLI11" for linked server "MY_LINKED_SERVER_NAME" was unable to begin a distributed transaction. error.

   Query Example:

   INSERT INTO dbo.Products
   DECLARE @MyQuery NVARCHAR(MAX) = 'SHOW TABLES';
   
   EXEC (@MyQuery) AT [LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY];
   

4. Finally, open a new query and execute a query we saved in one of the previous steps:
   

   SELECT * FROM OPENQUERY([LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY], 'SHOW TABLES')

   

   SELECT * FROM OPENQUERY([LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY], 'SHOW TABLES')

Create View in SQL Server

Finally, use this or similar query in a view or stored procedure, which you will be able to use in Tableau. We will create a view to return invoices:

1. CREATE VIEW vwApiInvoices AS
    SELECT * FROM OPENQUERY([LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY], 'SELECT * FROM Invoices')

Read data in Tableau from SQL Server

Actually, we will be getting data from SQL Server which in turn will be getting data from ZappySys Data Gateway data source. Let's begin and see how to accomplish that:

1. Open Tableau Desktop and click File > New.

2. To create new Connection click More > Microsoft SQL Server > Enter your credentials to connect to SQL Server (in our example before we used john):

   

3. Once connection is created for SQL Server we can read Salesforce Data Cloud (Data 360) data 3 different ways:

   1. Query View which contains OPENQUERY to Linked Server for Salesforce Data Cloud (Data 360) data
   2. Use direct SQL Query using OPENQUERY
   3. Use Stored Procedure (Mostly useful to parameterize calls

4. See below example to pull data from Salesforce Data Cloud (Data 360) in Tableau using SQL View approach:

   

5. Once your data sources are created you can click on Sheet1 and drag fields to create visualizations for Tableau Dashboard:

   

Passing Parameters to Salesforce Data Cloud (Data 360) calls in Tableau (Dynamic SQL)

1. First lets create a stored procedure in SQL Server for Parameter Example. Notice how we added WITH RESULT SETS in the code to describe metadata.

   --DROP PROC dbo.usp_GetInvoicesByCountry
   --GO
   /*
   Purpose: Parameterize Salesforce Data Cloud (Data 360) call via SQL. Call ZappySys Drivers inside SQL Server.
   */
   CREATE PROC dbo.usp_GetInvoicesByCountry
   	@country varchar(100) 
   AS 
   
   DECLARE @sql varchar(max)
   --//Escape single ticks carefully
   SET @sql =  'SELECT OrderID,CustomerID,Country,Quantity FROM $
   WITH (Src=''https://services.odata.org/V3/Northwind/Northwind.svc/Invoices?$format=json@filter=Country eq '+ @country +'''
   	 ,Filter=''$.value[*]''
   	 ,DataFormat=''OData''
   )'
   
   DECLARE @sqlFull varchar(max)
   SET @sqlFull='SELECT * FROM OPENQUERY([LS_TO_SALESFORCE_DATA_CLOUD_DATA_360_IN_GATEWAY], ''' + REPLACE( @sql, '''', '''''' ) + ''' )'
   PRINT @sqlFull --//For DEBUG purpose
   
   EXECUTE (@sqlFull) 
   WITH RESULT SETS ( 
    (OrderID int,CustomerID varchar(100),Country varchar(100),Quantity int) --//describe first result. If you don't do this then wont work in Tableau 
   )
   GO
   -- Example call
   EXEC dbo.usp_GetInvoicesByCountry @country='Germany'

2. Once you create a stored procedure go to Tableau datasource and select Database which contains the stored procedure we just created.
3. Now find your stored proc and drag it on the datasource pane. You will see parameters UI as below. You can create new parameter - Select New Parameter under Value Column.
4. Thats it now you can reuse your parameterized datasource anywhere in Dashboard.
5. If you have need to select Parameters from predefined values rather than free text then edit your parameter and select List option. Define values you like to select from as below.
6. When you create Tableau Dashboard you will see Parameter dropdown (If you selected List) elase you may see Textbox to enter custom value.

Firewall settings

So far we have assumed that Gateway is running on the same machine as SQL Server. However there will be a case when ZappySys ODBC PowerPack is installed on a different machine than SQL Server. In such case you may have to perform additional Firewall configurations. On most computers firewall settings wont allow outside traffic to ZappySys Data Gateway. In such case perform following steps to allow other machines to connect to Gateway.

If you are using newer version of ZappySys Data Gateway then adding firewall rule is just a single click.

1. Search for gateway in start menu and open ZappySys Data Gateway.
2. Go to Firewall Tab and click Add Firewall Rule button like below. This will create Firewall rule to all Inbound Traffic on Port 5000 (Unless you changed it).

Here is another way to add / edit Inbound Traffic rule in windows firewall. Use below method if you choose to customize your rule (for advanced users).

1. Search for Windows Firewall Advanced Security in start menu.
2. Under Inbound Rules > Right click and click [New Rule] >> Click Next
3. Select Port on Rule Type >> Click Next
4. Click on TCP and enter port number under specified local port as 5000 (use different one if you changed Default port) >> Click Next
5. Select Profile (i.e. Private, Public) >> Click Next
6. Enter Rule name [i.e. ZappySys Data Gateway – Allow Inbound ] >> Click Next
7. Click OK to save the rule

Troubleshooting

Validating JDBC connection in DBeaver

If you are experiencing JDBC connection issues, start by testing your JDBC driver in a JDBC client tool like DBeaver. If the JDBC connection fails in DBeaver, it naturally will not work in your ODBC data source either.

Create generic JDBC driver

1. Download and install DBeaver Community Edition.

2. Open DBeaver.

3. Click Database in the top menu and select Driver Manager:

   

4. Click the New button to start adding a custom JDBC driver:

   

5. Configure the connection settings by entering the Driver Name and Class Name (com.salesforce.datacloud.jdbc.DataCloudJDBCDriver):

   

   com.salesforce.datacloud.jdbc.DataCloudJDBCDriver

6. Go to the Libraries tab, click Add File, and select your Salesforce Data Cloud (Data 360) driver library file(s), e.g. C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar:

   
   Make sure to add all the required library dependencies.

7. Your JDBC driver jar library is now added:

   

   C:\ZappySys\Jdbc\Salesforce Data Cloud (Data 360)\jdbc-0.29.0-shaded.jar

8. (Optional). If required by your JDBC driver, add additional properties by going to the Default properties tab, Right-clicking on the background, and selecting Add new property:

   

9. Click on a value to modify it, then click OK to finish:

   

We are now ready to test the connection. Let's proceed!

Test connection

1. Click the New Database Connection icon in the toolbar:

   

2. Select your newly created JDBC driver from the list and click Next:

   

3. Enter your JDBC URL (e.g. jdbc:salesforce-datacloud://login.salesforce.com), click Test Connection to verify it works, and then click Finish:

   

   jdbc:salesforce-datacloud://login.salesforce.com

4. Finally, expand the database and table list to check the connection status:

   

There are two possible outcomes from the connection test:

• Reason:
  The JDBC driver works perfectly, meaning the issue lies within your ODBC data source configuration.
• Action:
  Double-check your ODBC data source configuration and ensure it matches the settings that successfully connected in DBeaver.

• Reason:
  There is likely an issue with the JDBC driver configuration or the connection details provided.
• Action:
  Contact the ZappySys Support Team for assistance.

If you are still experiencing issues or need further help, please contact us:

Frequent issues and solutions

Below are some useful community articles to help you troubleshoot and configure the ZappySys JDBC Bridge Driver:

• How to combine multiple JAR files
  Learn how to merge multiple .jar dependencies when your JDBC driver requires more than one file.
• How to fix JBR error: “Data lake is not available / Unable to verify trust for server certificate chain”
  Resolve SSL or certificate validation issues encountered during JDBC connections.
• System Exception: “Java is not installed or not accessible”
  Fix Java path or environment issues that prevent the JDBC Bridge from launching Java.
• JDBC Bridge Driver disconnect from Java host error
  Troubleshoot unexpected disconnection problems between your client application and the Java process.
• Error: Could not open jvm.cfg while using JDBC Bridge Driver
  Resolve JVM configuration path errors during driver initialization.
• How to enable JDBC Bridge Driver logging
  Enable detailed driver logging for better visibility during troubleshooting.
• How to pass JDBC connection parameters (not by URL)
  Learn how to specify connection properties programmatically instead of embedding them in the JDBC URL.
• How to fix JDBC Bridge error: “No connection could be made because the target machine actively refused it”
  Troubleshoot firewall or local port binding issues preventing communication with the Java host.
• How to use JDBC Bridge options (System Property for Java command line, e.g., classpath, proxy)
  Configure custom Java options like classpath and proxy using JDBC Bridge system properties.