![]() |
VOOZH | about |
Leverage existing skills by using the JDBC standard to connect to Calendly: Through drop-in integration into ETL tools like Oracle Data Integrator (ODI), the CData JDBC Driver for Calendly connects real-time Calendly data to your data warehouse, business intelligence, and Big Data technologies.
JDBC connectivity enables you to work with Calendly just as you would any other database in ODI. As with an RDBMS, you can use the driver to connect directly to the Calendly APIs in real time instead of working with flat files.
This article covers a JDBC-based ETL -- Calendly to Oracle. After reverse engineering a data model of Calendly entities, you will create a mapping and select a data loading strategy -- since the driver supports SQL-92, this last step can easily be accomplished by selecting the built-in SQL to SQL Loading Knowledge Module.
To install the driver, copy the driver JAR (cdata.jdbc.api.jar) and .lic file (cdata.jdbc.api.lic), located in the installation folder, into the ODI appropriate directory:
Restart ODI to complete the installation.
Reverse engineering the model retrieves metadata about the driver's relational view of Calendly data. After reverse engineering, you can query real-time Calendly data and create mappings based on Calendly tables.
Start by setting the Profile connection property to the location of the Calendly Profile on disk (e.g. C:\profiles\CalendlyProfile.apip). Next, set the ProfileSettings connection property to the connection string for Calendly (see below).
To authenticate to Calendly, provide an API Key. The Calendly API Key, can be found in your Calendly account, under 'Integrations' > 'API & Webhooks' > 'Generate New Token'. Set the APIKey in the ProfileSettings connection property.
For assistance in constructing the JDBC URL, use the connection string designer built into the Calendly JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.api.jar
Fill in the connection properties and copy the connection string to the clipboard.
π Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)Below is a typical connection string:
jdbc:api:Profile=C:\profiles\Calendly.apip;ProfileSettings='APIKey=your_api_token';
After reverse engineering you can now work with Calendly data in ODI.
To view Calendly data, expand the Models accordion in the Designer navigator, right-click a table, and click View data.
π Viewing the data.
Follow the steps below to create an ETL from Calendly. You will load OrganizationScheduledEvents entities into the sample data warehouse included in the ODI Getting Started VM.
Open SQL Developer and connect to your Oracle database. Right-click the node for your database in the Connections pane and click new SQL Worksheet.
Alternatively you can use SQLPlus. From a command prompt enter the following:
sqlplus / as sysdba
CREATE TABLE ODI_DEMO.TRG_ORGANIZATIONSCHEDULEDEVENTS (NAME NUMBER(20,0),Uri VARCHAR2(255));
You can then run the mapping to load Calendly data into Oracle.
Connect to live data from Calendly with the API Driver
Connect to Calendly