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 →Configure the CData JDBC Driver for Dynamics 365 in a Connection Pool in Tomcat
Connect to Dynamics 365 data from a connection pool in Tomcat.
The CData JDBC Drivers support standard JDBC interfaces to integrate with Web applications running on the JVM. This article details how to connect to Dynamics 365 data from a connection pool in Tomcat.
About Dynamics 365 Data Integration
CData simplifies access and integration of live Microsoft Dynamics 365 data. Our customers leverage CData connectivity to:
- Read and write data in the full Dynamics 365 ecosystem: Sales, Customer Service, Finance & Operations, Marketing, and more.
- Extend the native features of Dynamics CRM with customizable caching and intelligent query aggregation and separation.
- Authenticate securely with Dynamics 365 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 their Dynamics 365 entities - listing, creating, and removing associations between entities.
CData customers use our Dynamics 365 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 Dynamics 365 data from their preferred data tools inside the Microsoft ecosystem (Power BI, Excel, etc.) or with external tools (Tableau, Looker, etc.).
Getting Started
Connect to Dynamics 365 Data through a Connection Pool in Tomcat
- Copy the CData JAR and CData .lic file to $CATALINA_HOME/lib. The CData JAR is located in the lib subfolder of the installation directory.
- Add a definition of the resource to the context. Specify the JDBC URL here.
Edition and OrganizationUrl are required connection properties. The Dynamics 365 connector supports connecting to the following editions: CustomerService, FieldService, FinOpsOnline, FinOpsOnPremise, HumanResources, Marketing, ProjectOperations and Sales.
For Dynamics 365 Business Central, use the separate Dynamics 365 Business Central driver.
OrganizationUrl is the URL to your Dynamics 365 organization. For instance, https://orgcb42e1d0.crm.dynamics.com
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Dynamics 365 JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.dynamics365.jar
Fill in the connection properties and copy the connection string to the clipboard.
You can see the JDBC URL specified in the resource definition below.
<Resource name="jdbc/dynamics365" auth="Container" type="javax.sql.DataSource" driverClassName="cdata.jdbc.dynamics365.Dynamics365Driver" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" url="jdbc:dynamics365:OrganizationUrl=https://myaccount.operations.dynamics.com/;Edition=Sales;InitiateOAuth=GETANDREFRESH" maxActive="20" maxIdle="10" maxWait="-1" />
To allow a single application to access Dynamics 365 data, add the code above to the context.xml in the application's META-INF directory.
For a shared resource configuration, add the code above to the context.xml located in $CATALINA_BASE/conf. A shared resource configuration provides connectivity to Dynamics 365 for all applications.
- Add a reference to the resource to the web.xml for the application.
Dynamics 365 data JSP jdbc/Dynamics365 javax.sql.DataSource Container -
Initialize connections from the connection pool:
Context initContext = new InitialContext(); Context envContext = (Context)initContext.lookup("java:/comp/env"); DataSource ds = (DataSource)envContext.lookup("jdbc/Dynamics365"); Connection conn = ds.getConnection();
More Tomcat Integration
The steps above show how to connect to Dynamics 365 data in a simple connection pooling scenario. For more use cases and information, see the JNDI Datasource How-To in the Tomcat documentation.