![]() |
VOOZH | about |
Leverage existing skills by using the JDBC standard to read and write to Sage Intacct: Through drop-in integration into ETL tools like Oracle Data Integrator (ODI), the CData JDBC Driver for Sage Intacct connects real-time Sage Intacct data to your data warehouse, business intelligence, and Big Data technologies.
JDBC connectivity enables you to work with Sage Intacct just as you would any other database in ODI. As with an RDBMS, you can use the driver to connect directly to the Sage Intacct APIs in real time instead of working with flat files.
This article covers a JDBC-based ETL -- Sage Intacct to Oracle. After reverse engineering a data model of Sage Intacct 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.
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.
To install the driver, copy the driver JAR (cdata.jdbc.sageintacct.jar) and .lic file (cdata.jdbc.sageintacct.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 Sage Intacct data. After reverse engineering, you can query real-time Sage Intacct data and create mappings based on Sage Intacct tables.
To 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
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:sageintacct:User=myusername;CompanyId=TestCompany;Password=mypassword;SenderId=Test;SenderPassword=abcde123;
After reverse engineering you can now work with Sage Intacct data in ODI.
To edit and save Sage Intacct data, expand the Models accordion in the Designer navigator, right-click a table, and click Data. Click Refresh to pick up any changes to the data. Click Save Changes when you are finished making changes.
π Viewing the data.
Follow the steps below to create an ETL from Sage Intacct. You will load Customer 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_CUSTOMER (TOTALDUE NUMBER(20,0),Name VARCHAR2(255));
You can then run the mapping to load Sage Intacct data into Oracle.
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.