![]() |
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 Sage Intacct data.
This tutorial explains how to build a simple ETL validator data flow to extract data from Sage Intacct data and load it into an example data storage solution: SQL Server.
CData provides the easiest way to access and integrate live data from Sage Intact. Customers use CData connectivity to:
Users frequently integrate Sage Intact with analytics tools such as Tableau, Power BI, and Excel, and leverage our tools to replicate Workday data to databases or data warehouses.
To learn about how other customers are using CData's Sage Intacct solutions, check out our blog: Drivers in Focus: Accounting Connectivity.
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 Sage Intacct 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 Sage Intacct in ETL Validator.
π CData data sourceTo connect using the Login method, the following connection properties are required: User, Password, CompanyId, SenderId and SenderPassword.
User, Password, and CompanyId are the credentials for the account you wish to connect to.
SenderId and SenderPassword are the Web Services credentials assigned to you by Sage Intacct.
For assistance in constructing the JDBC URL, use the connection string designer built into the Sage Intacct JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.sageintacct.jar
π Using the built-in connection string designer to generate a JDBC URL (sage intacct is shown.)
A typical connection string looks like this:
jdbc:sageintacct:User=myusername;CompanyId=TestCompany;Password=mypassword;SenderId=Test;SenderPassword=abcde123;
To ensure the JDBC driver is licensed appropriately, copy the license file to the appropriate location:
Copy the JDBC Driver for Sage Intacct and lic file from "C:\Program Files\CData[product_name]\lib" to "C:\Datagaps\ETLValidator\Server\apache-tomcat\bin".
cdata.jdbc.sageintacct.jar cdata.jdbc.sageintacct.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 Sage Intacct 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 Sage Intacct 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 Sage Intacct data to SQL Server.
π Full dataflowDownload a free, 30-day trial of the CData JDBC Driver for Sage Intacct and start building Sage Intacct-connected applications with ETL Validator. Reach out to our Support Team if you have any questions.
Download a free trial of the Sage Intacct Driver to get started:
Download NowLearn more:
π Sage Intacct IconComplete read-write access to Sage Intacct enables developers to search (Contacts, Invoices, Transactions, Vendors, etc.), update items, edit customers, and more, from any Java/J2EE application.