Connect to Microsoft Planner Data from a Connection Pool in Jetty

Ready to get started?

Download for a free trial:

Download Now

Learn more:

Microsoft Planner JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with Microsoft Planner.



The Microsoft Planner JDBC Driver supports connection pooling: This article shows how to connect faster to Microsoft Planner data from Web apps in Jetty.

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

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 Microsoft Planner data source at the level of the Web app, in WEB-INF\jetty-env.xml.

    <Configure id='msplannerdemo' class="org.eclipse.jetty.webapp.WebAppContext"> <New id="msplannerdemo" class="org.eclipse.jetty.plus.jndi.Resource"> <Arg><Ref refid="msplannerdemo"/></Arg> <Arg>jdbc/msplannerdb</Arg> <Arg> <New class="cdata.jdbc.microsoftplanner.MicrosoftPlannerDriver"> <Set name="url">jdbc:microsoftplanner:</Set> <Set name="OAuthClientId">MyApplicationId</Set> <Set name="OAuthClientSecret">MySecretKey</Set> <Set name="CallbackURL">http://localhost:33333</Set> <Set name="InitiateOAuth">GETANDREFRESH</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.
    • 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 Driver opens the MS Planner OAuth endpoint in your default browser. Log in and grant permissions to the Driver. The Driver then completes the OAuth process.

    1. Extracts the access token from the callback URL and authenticates requests.
    2. Obtains a new access token when the old one expires.
    3. Saves OAuth values in OAuthSettingsLocation to be persisted across connections.
  4. Configure the resource in the Web.xml:

    jdbc/msplannerdb javax.sql.DataSource Container
  5. You can then access Microsoft Planner with a lookup to java:comp/env/jdbc/msplannerdb: InitialContext ctx = new InitialContext(); DataSource mymsplanner = (DataSource)ctx.lookup("java:comp/env/jdbc/msplannerdb");

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.