Connect to HCL Domino Data from a Connection Pool in Jetty

The CData JDBC driver for HCL Domino is easy to integrate with Java Web applications. This article shows how to efficiently connect to HCL Domino data in Jetty by configuring the driver for connection pooling. You will configure a JNDI resource for HCL Domino 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 HCL Domino data source at the level of the Web app, in WEB-INF\jetty-env.xml.

   <Configure id='dominodemo' class="org.eclipse.jetty.webapp.WebAppContext">
    <New id="dominodemo" class="org.eclipse.jetty.plus.jndi.Resource">
    <Arg><Ref refid="dominodemo"/></Arg>
    <Arg>jdbc/dominodb</Arg>
    <Arg>
    <New class="cdata.jdbc.domino.DominoDriver">
    <Set name="url">jdbc:domino:</Set>
    <Set name="Server">https://domino.corp.com</Set>
    <Set name="AuthScheme">OAuthPassword</Set>
    <Set name="User">my_domino_user</Set>
    <Set name="Password">my_domino_password</Set>
    </New>
    </Arg>
    </New>
   </Configure>
   

   Connecting to Domino

   To connect to Domino data, set the following properties:

   • URL: The host name or IP of the server hosting the Domino database. Include the port of the server hosting the Domino database. For example: http://sampleserver:1234/
   • DatabaseScope: The name of a scope in the Domino Web UI. The driver exposes forms and views for the schema governed by the specified scope. In the Domino Admin UI, select the Scopes menu in the sidebar. Set this property to the name of an existing scope.

   Authenticating with Domino

   Domino supports authenticating via login credentials or an Entra ID (formerly Azure AD) OAuth application:

   Login Credentials

   To authenticate with login credentials, set the following properties:

   • AuthScheme: Set this to "OAuthPassword"
   • User: The username of the authenticating Domino user
   • Password: The password associated with the authenticating Domino user

   The driver uses the login credentials to automatically perform an OAuth token exchange.

   EntraID (formerly AzureAD)

   This authentication method uses Entra ID (formerly Azure AD) as an IdP to obtain a JWT token. You need to create a custom OAuth application in Entra ID (formerly Azure AD) and configure it as an IdP. To do so, follow the instructions in the Help documentation. Then set the following properties:

   • AuthScheme: Set this to "EntraID (formerly AzureAD)"
   • InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
   • OAuthClientId: The Client ID obtained when setting up the custom OAuth application.
   • OAuthClientSecret: The Client secret obtained when setting up the custom OAuth application.
   • CallbackURL: The redirect URI defined when you registered your app. For example: https://localhost:33333
   • AzureTenant: The Microsoft Online tenant being used to access data. Supply either a value in the form companyname.microsoft.com or the tenant ID.

     The tenant ID is the same as the directory ID shown in the Azure Portal's Entra ID (formerly Azure AD) > Properties page.

4. Configure the resource in the Web.xml:

    jdbc/dominodb
    javax.sql.DataSource
    Container
   
   

5. You can then access HCL Domino with a lookup to java:comp/env/jdbc/dominodb:

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

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.