VOOZH about

URL: https://www.cdata.com/kb/tech/dynamics365-jdbc-jetty.rst

⇱ Connect to Dynamics 365 Data from a Connection Pool in Jetty

Connect to Dynamics 365 Data from a Connection Pool in Jetty

👁 Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
The Dynamics 365 JDBC Driver supports connection pooling: This article shows how to connect faster to Dynamics 365 data from Web apps in Jetty.

The CData JDBC driver for Dynamics 365 is easy to integrate with Java Web applications. This article shows how to efficiently connect to Dynamics 365 data in Jetty by configuring the driver for connection pooling. You will configure a JNDI resource for Dynamics 365 in Jetty.

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


Configure the JDBC Driver for Salesforce as a JNDI Data Source

Follow the steps below to connect to Salesforce from Jetty.

  1. 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
  2. Add the CData and license file, located in the lib subfolder of the installation directory, into the lib subfolder of the context path.

  3. Declare the resource and its scope. Enter the required connection properties in the resource declaration. This example declares the Dynamics 365 data source at the level of the Web app, in WEB-INF\jetty-env.xml. 

    <Configure id='dynamics365demo' class="org.eclipse.jetty.webapp.WebAppContext">
 <New id="dynamics365demo" class="org.eclipse.jetty.plus.jndi.Resource">
 <Arg><Ref refid="dynamics365demo"/></Arg>
 <Arg>jdbc/dynamics365db</Arg>
 <Arg>
 <New class="cdata.jdbc.dynamics365.Dynamics365Driver">
 <Set name="url">jdbc:dynamics365:</Set>
 <Set name="OrganizationUrl">https://myaccount.operations.dynamics.com/</Set>
 <Set name="Edition">Sales</Set>
 <Set name="InitiateOAuth">GETANDREFRESH</Set>
 </New>
 </Arg>
 </New>
</Configure>

    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

  4. Configure the resource in the Web.xml: 

     jdbc/dynamics365db
 javax.sql.DataSource
 Container

  5. You can then access Dynamics 365 with a lookup to java:comp/env/jdbc/dynamics365db: 

    InitialContext ctx = new InitialContext();
DataSource mydynamics365 = (DataSource)ctx.lookup("java:comp/env/jdbc/dynamics365db");

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.