Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Add Typeform Data to Informatica Enterprise Data Catalog
Use the CData JDBC Driver for Typeform with the Informatica Enterprise Data Catalog to classify and organize data.
Informatica provides a powerful, elegant means of transporting and transforming your data. By utilizing the CData JDBC Driver for Typeform, you are gaining access to a driver based on industry-proven standards that integrates seamlessly with Informatica's Enterprise Data Catalog. This tutorial shows how to classify and organize Typeform data across any environment.
Load the JDBC Driver
To load the JDBC Driver:
- Install the JDBC Driver on the host running Informatica. For this article, it is assumed that the driver was installed into cdata.jdbc.api.APIDriver.
- Navigate to the JDBC install directory and create a zip file called genericJDBC.zip containing the driver and its license file.
- Move the genericJDBC.zip file into the Catalog Service directory within Informatica. For this article, it is assumed that Informatica is installed into /opt/informatica. Working in this folder will probably require root permissions, so make sure to su or sudo to root before continuing.
- Edit the custom deployment configuration to unpack the zip file.
- Refresh the Catalog Service from the Admin console.
$ java -jar setup.jar
$ cd ~/cdata-jdbc-driver-for-api/lib
$ zip genericJDBC.zip cdata.jdbc.api.jar cdata.jdbc.api.lic
# mv genericJDBC.zip /opt/informatica/services/CatalogService/ScannerBinaries
# cd /opt/informatica/services/CatalogService/ScannerBinaries/CustomDeployer/
# nano scannerDeployer.xml
After unpacking the existing ExecutionContextProperty nodes, add a new ExecutionContextProperty node with this content.
<ExecutionContextProperty
isLocationProperty="true"
dependencyToUnpack="genericJDBC.zip">
<PropertyName>JDBCScanner_DriverLocation</PropertyName>
<PropertyValue>scanner_miti/genericJDBC/Drivers</PropertyValue>
</ExecutionContextProperty>
Configure the JDBC Resource
To configure the JDBC resource:
- Open the Catalog administrator and add a new JDBC resource with the following properties:
- Driver Class: cdata.jdbc.api.APIDriver
- URL: jdbc.api:Profile=C:\profiles\TypeForm.apip;Authscheme=OAuth;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;CallbackUrl=your_callback_url;InitiateOAuth=GETANDREFRESH;
- CData Desktop Applications: CData desktop applications (Sync, API Server, ArcESB) accept OAuth tokens at /src/oauthCallback.rst. The host and port is the same as the default port used by the application. For example, if you use http://localhost:8019/ to access CData Sync then the redirect URI will be http://localhost:8019/src/oauthCallback.rst.
- CData Cloud Applications: CData cloud applications are similar to their desktop counterparts. If you access Connect Cloud at https://1.2.3.4/ then you should use the redirect https://1.2.3.4/src/oauthCallback.rst.
- Desktop Application: When using a desktop application, the URI https://localhost:33333 is recommended.
- Web Application: When developing a web application using the driver, use your own URI here such as https://my-website.com/oauth.
- AuthScheme: Set this to OAuth.
- InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to manage the process to obtain the OAuthAccessToken.
- OAuthClientId: Set this to the Client Id that is specified in your app settings.
- OAuthClientSecret: Set this to Client Secret that is specified in your app settings.
- CallbackURL: Set this to the Redirect URI you specified in your app settings.
- Username: user
- Password: password
- Configure the metadata options to perform at least one source metadata scan. This scan uses the driver to determine what tables, views, and stored procedures are available through the service.
- Source Metadata: Enable this option.
- Catalog: Set this to the appropriate catalog for multi-catalog data sources. Otherwise, set this to CData.
- Schema: Set this to the appropriate schema for multi-schema data sources. Otherwise, set this to the name of the service (for example, Couchbase).
- Case-sensitivity: Generally this option should be disabled. Enable it only for data sources which are case-sensitive.
- Import stored procedures: Enable this if you want to import stored procedure definitions in addition to tables and views.
- Complete the driver configuration, optionally configuring custom attributes and a scanner schedule.
- Perform the metadata scan by navigating to the Monitoring tab and clicking Run. Depending upon the data source, this may takes a few minutes.
Start by setting the Profile connection property to the location of the TypeForm Profile on disk (e.g. C:\profiles\TypeForm.apip). Next, set the ProfileSettings connection property to the connection string for TypeForm (see below).
TypeForm API Profile Settings
Authentication to TypeForm uses the OAuth standard.
To authenticate to TypeForm, you must first register and configure an OAuth application with TypeForm here: https://admin.typeform.com/account#/section/tokens. Your app will be assigned a client ID and a client secret which can be set in the connection string. More information on setting up an OAuth application can be found at https://developer.typeform.com/get-started/.
Note that there are several different use scenarios which all require different redirect URIs:
After setting the following connection properties, you are ready to connect:
Built-In Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Typeform 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.
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.
Typical additional connection string properties follow:
JDBC;MSTR_JDBC_JAR_FOLDER=PATH\TO\JAR\;DRIVER=cdata.jdbc.api.APIDriver;URL={jdbc:api:Profile=C:\profiles\TypeForm.apip;Authscheme=OAuth;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;CallbackUrl=your_callback_url;};
Note that the Username and Password properties are required, even if the driver you are using does not require them. In those cases, you can enter a placeholder value instead.
Other metadata scanners may be enabled as desired.
When the scan is complete, a summary of all of the metadata objects is displayed along with the status of the Metadata Load job. If any errors occur, you can open the Log Location link for the job to see the errors reported by Informatica or the driver.
Validate the Discovered Metadata
Open the Catalog Service browser to view the metadata extracted from the data source. Depending upon the options you selected when configuring the metadata scanner, you may see any combination of tables, views, and stored procedures for the resource you defined.