Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →How to connect to Salesloft Data in DBVisualizer
Integrate Salesloft data with visual data analysis tools and data connection wizards in DBVisualizer
The CData JDBC Driver for Salesloft implements JDBC standards to provide connectivity to Salesloft data in applications ranging from business intelligence tools to IDEs. This article shows how to establish a connection to Salesloft data in DBVisualizer and use the table editor to edit and save Salesloft data.
Create a New Driver Definition for Salesloft Data
Follow the steps below to use the Driver Manager to provide connectivity to Salesloft data from DBVisualizer tools.
- In DBVisualizer, click Tools -> Driver Manager.
- Click the plus sign "" to create a new driver.
- Select "Custom" as the template.
- On the Driver Settings tab:
- Set Name to a user-friendly name (e.g. "CData Salesloft Driver")
- Set URL Format to jdbc:salesloft:
- In Driver artifacts and jar files (jars are loaded in order from top):
- Click the plus sign "" -> "Add Files"
- Navigate to the "lib" folder in the installation directory (C:\Program Files\CData[product_name] XXXX\)
- Select the JAR file (cdata.jdbc.SalesLoft.jar) and click "Open"
- The Driver Class should populate automatically. If not, select class (cdata.jdbc.salesloft.SalesLoftDriver).
Define the Connection to the JDBC Data Source
Close the "Driver Manager" and follow the steps below to save connection properties in the JDBC URL.
- In the "Databases" tab, click the plus sign "" and select the driver you just created.
In the "Connection" section, set the following options:
- Database Type: If you selected the wizard option, the database type is automatically detected. If you selected the "No Wizard" option, select the Generic or Auto Detect option in the Database Type menu.
- Driver Type: Select the driver you just created.
Database URL: Enter the full JDBC URL. The syntax of the JDBC URL is jdbc:salesloft: followed by the connection properties in a semicolon-separated list of name-value pairs.
SalesLoft authenticates using the OAuth authentication standard or an API Key. OAuth requires the authenticating user to interact with SalesLoft using the browser.
Using OAuth
For OAuth authentication, create an OAuth app to obtain the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties. See the OAuth section in the Help documentation for an authentication guide.Using APIKey
Alternatively, you can authenticate with an APIKey. Provision an API key from the SalesLoft user interface: https://accounts.salesloft.com/oauth/applications/. You will receive a Key which will be used when issuing requests.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Salesloft JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.salesloft.jar
Fill in the connection properties and copy the connection string to the clipboard.
When you configure the JDBC URL, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
A typical connection string is below:
jdbc:salesloft:AuthScheme=OAuth;OAuthClientId=MyOAuthClientId;OAuthClientSecret=MyOAuthClientSecret;CallbackUrl=http://localhost:33333;InitiateOAuth=GETANDREFRESH
- NOTE: Since Salesloft does not require a User or Password to authenticate, you may use whatever values you wish for Database Userid and Database Password.
- On the Connection tab, click Connect.
To browse through tables exposed by the Salesloft JDBC Driver, right-click a table and click "Open in New Tab."
To execute SQL queries, use the SQL Commander tool: Click SQL Commander -> New SQL Commander. Select the Database Connection, Database, and Schema from the available menus.
See the "Supported SQL" chapter in the help documentation for more information on the supported SQL. See the "Data Model" chapter for table-specific information.