Connect to Cvent Data from a Connection Pool in Jetty

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

   <Configure id='cventdemo' class="org.eclipse.jetty.webapp.WebAppContext">
    <New id="cventdemo" class="org.eclipse.jetty.plus.jndi.Resource">
    <Arg><Ref refid="cventdemo"/></Arg>
    <Arg>jdbc/cventdb</Arg>
    <Arg>
    <New class="cdata.jdbc.cvent.CventDriver">
    <Set name="url">jdbc:cvent:</Set>
    <Set name="OAuthClientId">MyOAuthClientId</Set>
    <Set name="OAuthClientSecret">MyOAuthClientSecret</Set>
    <Set name="InitiateOAuth">GETANDREFRESH</Set>
    </New>
    </Arg>
    </New>
   </Configure>
   

   Before you can authenticate to Cvent, you must create a workspace and an OAuth application.

   Creating a Workspace

   To create a workspace:

   1. Sign into Cvent and navigate to App Switcher (the blue button in the upper right corner of the page) >> Admin.
   2. In the Admin menu, navigate to Integrations >> REST API.
   3. A new tab launches for Developer Management. Click on Manage API Access in the new tab.
   4. Create a Workspace and name it. Select the scopes you would like your developers to have access to. Scopes control what data domains the developer can access.
      • Choose All to allow developers to choose any scope, and any future scopes added to the REST API.
      • Choose Custom to limit the scopes developers can choose for their OAuth apps to selected scopes. To access all tables exposed by the driver, you need to set the following scopes:

        event/attendees:read	event/attendees:write	event/contacts:read
        event/contacts:write	event/custom-fields:read	event/custom-fields:write
        event/events:read	event/events:write	event/sessions:delete
        event/sessions:read	event/sessions:write	event/speakers:delete
        event/speakers:read	event/speakers:write	budget/budget-items:read
        budget/budget-items:write	exhibitor/exhibitors:read	exhibitor/exhibitors:write
        survey/surveys:read	survey/surveys:write

   Creating an OAuth Application

   After you have set up a Workspace and invited them, developers can sign up and create a custom OAuth app. See the Creating a Custom OAuth Application section in the Help documentation for more information.

   Connecting to Cvent

   After creating an OAuth application, set the following connection properties to connect to Cvent:

   • InitiateOAuth: GETANDREFRESH. Used to automatically get and refresh the OAuthAccessToken.
   • OAuthClientId: The Client ID associated with the OAuth application. You can find this on the Applications page in the Cvent Developer Portal.
   • OAuthClientSecret: The Client secret associated with the OAuth application. You can find this on the Applications page in the Cvent Developer Portal.

4. Configure the resource in the Web.xml:

    jdbc/cventdb
    javax.sql.DataSource
    Container
   
   

5. You can then access Cvent with a lookup to java:comp/env/jdbc/cventdb:

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

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.