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 Microsoft Dataverse Data from a Connection Pool in Jetty
The Microsoft Dataverse JDBC Driver supports connection pooling: This article shows how to connect faster to Microsoft Dataverse data from Web apps in Jetty.
The CData JDBC driver for Microsoft Dataverse is easy to integrate with Java Web applications. This article shows how to efficiently connect to Microsoft Dataverse data in Jetty by configuring the driver for connection pooling. You will configure a JNDI resource for Microsoft Dataverse in Jetty.
About Microsoft Dataverse Data Integration
CData provides the easiest way to access and integrate live data from Microsoft Dataverse (formerly the Common Data Service). Customers use CData connectivity to:
- Access both Dataverse Entities and Dataverse system tables to work with exactly the data they need.
- Authenticate securely with Microsoft Dataverse in a variety of ways, including Azure Active Directory, Azure Managed Service Identity credentials, and Azure Service Principal using either a client secret or a certificate.
- Use SQL stored procedures to manage Microsoft Dataverse entities - listing, creating, and removing associations between entities.
CData customers use our Dataverse connectivity solutions for a variety of reasons, whether they're looking to replicate their data into a data warehouse (alongside other data sources)or analyze live Dataverse data from their preferred data tools inside the Microsoft ecosystem (Power BI, Excel, etc.) or with external tools (Tableau, Looker, etc.).
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 Microsoft Dataverse data source at the level of the Web app, in WEB-INF\jetty-env.xml.
<Configure id='dataversedemo' class="org.eclipse.jetty.webapp.WebAppContext"> <New id="dataversedemo" class="org.eclipse.jetty.plus.jndi.Resource"> <Arg><Ref refid="dataversedemo"/></Arg> <Arg>jdbc/dataversedb</Arg> <Arg> <New class="cdata.jdbc.cds.CDSDriver"> <Set name="url">jdbc:cds:</Set> <Set name="OrganizationUrl">https://myaccount.crm.dynamics.com/InitiateOAuth</Set> </New> </Arg> </New> </Configure>
You can connect without setting any connection properties for your user credentials. Below are the minimum connection properties required to connect.
- InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
- OrganizationUrl: Set this to the organization URL you are connecting to, such as https://myorganization.crm.dynamics.com.
- Tenant (optional): Set this if you wish to authenticate to a different tenant than your default. This is required to work with an organization not on your default Tenant.
When you connect the Common Data Service OAuth endpoint opens in your default browser. Log in and grant permissions. The OAuth process completes automatically.
-
Configure the resource in the Web.xml:
jdbc/dataversedb javax.sql.DataSource Container -
You can then access Microsoft Dataverse with a lookup to java:comp/env/jdbc/dataversedb:
InitialContext ctx = new InitialContext(); DataSource mydataverse = (DataSource)ctx.lookup("java:comp/env/jdbc/dataversedb");
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.