Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Connect to Sage Intacct Data from a Connection Pool in Jetty
The Sage Intacct JDBC Driver supports connection pooling: This article shows how to connect faster to Sage Intacct data from Web apps in Jetty.
The CData JDBC driver for Sage Intacct is easy to integrate with Java Web applications. This article shows how to efficiently connect to Sage Intacct data in Jetty by configuring the driver for connection pooling. You will configure a JNDI resource for Sage Intacct in Jetty.
About Sage Intacct Data Integration
CData provides the easiest way to access and integrate live data from Sage Intact. Customers use CData connectivity to:
- Access Sage Intacct without worrying about API updates or changes.
- Access custom objects and fields in Sage Intacct with no extra configuration steps involved.
- Write data back to Sage Intacct using embedded Web Services credentials with Basic authentication.
- Use SQL stored procedures to perform functional operations like approving or declining vendors, inserting engagements, and creating or deleting custom objects or fields.
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.
Getting Started
Configure the JDBC Driver for Salesforce as a JNDI Data Source
Follow the steps below to connect to Salesforce from Jetty.
Enable the JNDI module for your Jetty base. The following command enables JNDI from the command-line:
java -jar ../start.jar --add-to-startd=jndi
- Add the CData and license file, located in the lib subfolder of the installation directory, into the lib subfolder of the context path.
-
Declare the resource and its scope. Enter the required connection properties in the resource declaration. This example declares the Sage Intacct data source at the level of the Web app, in WEB-INF\jetty-env.xml.
<Configure id='intacctdemo' class="org.eclipse.jetty.webapp.WebAppContext"> <New id="intacctdemo" class="org.eclipse.jetty.plus.jndi.Resource"> <Arg><Ref refid="intacctdemo"/></Arg> <Arg>jdbc/intacctdb</Arg> <Arg> <New class="cdata.jdbc.sageintacct.SageIntacctDriver"> <Set name="url">jdbc:sageintacct:</Set> <Set name="User">myusername</Set> <Set name="CompanyId">TestCompany</Set> <Set name="Password">mypassword</Set> <Set name="SenderId">Test</Set> <Set name="SenderPassword">abcde123</Set> </New> </Arg> </New> </Configure>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.
-
Configure the resource in the Web.xml:
jdbc/intacctdb javax.sql.DataSource Container
-
You can then access Sage Intacct with a lookup to java:comp/env/jdbc/intacctdb:
InitialContext ctx = new InitialContext(); DataSource myintacct = (DataSource)ctx.lookup("java:comp/env/jdbc/intacctdb");
More Jetty Integration
The steps above show how to configure the driver in a simple connection pooling scenario. For more use cases and information, see the Working with Jetty JNDI chapter in the Jetty documentation.