![]() |
VOOZH | about |
ETL Validator provides data movement and transformation capabilities for integrating data platforms across your organization. CData's JDBC driver seamlessly integrates with ETL Validator and extends its native connectivity to include Anaplan data.
This tutorial explains how to build a simple ETL validator data flow to extract data from Anaplan data and load it into an example data storage solution: SQL Server.
CData extends ETL Validator's data connectivity capabilities by providing the ability to add data sources that connect via CData's JDBC drivers. Connecting to Anaplan data simply requires creating a new data source in ETL Validator through CData's connectiviy suite as described below.
Begin by logging into ETL Validator to view the application dashboard.
π Access the ETL Validator dashboardCData extends the data source options within ETL Validator.
π Create a new DataSourceCData's connectivity is embedded within ETL Validator's data source options.
π CData data sourceYou will need a JDBC connection string to establish a connection to Anaplan in ETL Validator.
π CData data sourceThe driver supports authenticating with Basic, Certificate, or OAuth. In every case, set Region to the region where your Anaplan account data is hosted (e.g., , which is the default).
Set AuthScheme to , then supply your Anaplan User and Password. If your workspace uses single sign-on (SSO), you must be assigned as an Exception User to use Basic authentication.
Set AuthScheme to , then supply the Certificate, CertificateType, and PrivateKey properties (and the matching CertificatePassword / PrivateKeyPassword if either is encrypted). The certificate must be a CA-issued X.509 certificate registered with your Anaplan tenant administrator.
Register a custom OAuth application in Anaplan, then set the following properties:
See the Getting Started chapter of the help documentation for a guide to creating a custom OAuth app and using OAuth.
For assistance in constructing the JDBC URL, use the connection string designer built into the Anaplan JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.anaplan.jar
π Using the built-in connection string designer to generate a JDBC URL (anaplan is shown.)
A typical connection string looks like this:
jdbc:anaplan:OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;CallbackURL=your_callback_url;Region=US1;InitiateOAuth=GETANDREFRESH;
To ensure the JDBC driver is licensed appropriately, copy the license file to the appropriate location:
Copy the JDBC Driver for Anaplan and lic file from "C:\Program Files\CData[product_name]\lib" to "C:\Datagaps\ETLValidator\Server\apache-tomcat\bin".
cdata.jdbc.anaplan.jar cdata.jdbc.anaplan.lic
Note: If you do not copy the .lic file with the jar, you will see a licensing error that indicates you do not have a valid license installed. This is true for both the trial and full versions.
Should you encounter any difficulties loading the CData JDBC driver class, please contact DataGap's team, and they will provide you instructions on how to load the jar file for the relevant driver.
This example will use SQL Server as a destination for Anaplan data data, but any preferred destination can be used instead.
This option is the default.
π Add SQL ServerThe details will depend on the specific target, but these details may include a URL, authentiation credentials, etc.
π Add SQL ServerConfigured data flows will appear in this window.
π Dataflows tabName your new dataflow and save it.
The details of the data movement will be configured in this panel.
π Dataflow diagramGive the new source an appropriate name and save it.
π Jira example sourceSelect the Table from the Schema option that reflects which data should be pulled from Anaplan data.
The anticipated outcome of the configured query is displayed in the Result tab.
π Query resultsSelect Switch to Diagram, then drag & drop the DB Sink as a target from the right side (under Sink options). Give the sink an appropriate name and save it.
π Data sinkChoose the Schema and table that matches the structure of the source table. For this example, the table on the target side was created to match the Source so that data flow seamlessly. More advanced schema transformation operations are beyond the scope of this article.
π Destination schemaRunning the job will take some time.
π Destination schemaReturn to the diagram to see the finished data replication job from Anaplan data to SQL Server.
π Full dataflowDownload a free, 30-day trial of the CData JDBC Driver for Anaplan and start building Anaplan-connected applications with ETL Validator. Reach out to our Support Team if you have any questions.
Download a free trial of the Anaplan Driver to get started:
Download NowLearn more:
π Anaplan IconRapidly create and deploy powerful Java applications that integrate with Anaplan.