Connect to Bitbucket Data from a Connection Pool in Jetty

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

   <Configure id='bitbucketdemo' class="org.eclipse.jetty.webapp.WebAppContext">
    <New id="bitbucketdemo" class="org.eclipse.jetty.plus.jndi.Resource">
    <Arg><Ref refid="bitbucketdemo"/></Arg>
    <Arg>jdbc/bitbucketdb</Arg>
    <Arg>
    <New class="cdata.jdbc.bitbucket.BitbucketDriver">
    <Set name="url">jdbc:bitbucket:</Set>
    <Set name="Workspace">myworkspaceslug</Set>
    <Set name="Schema">Information</Set>
    <Set name="InitiateOAuth">GETANDREFRESH</Set>
    </New>
    </Arg>
    </New>
   </Configure>
   

   For most queries, you must set the Workspace. The only exception to this is the Workspaces table, which does not require this property to be set, as querying it provides a list of workspace slugs that can be used to set Workspace. To query this table, you must set Schema to 'Information' and execute the query SELECT * FROM Workspaces>.

   Setting Schema to 'Information' displays general information. To connect to Bitbucket, set these parameters:

   • Schema: To show general information about a workspace, such as its users, repositories, and projects, set this to Information. Otherwise, set this to the schema of the repository or project you are querying. To get a full set of available schemas, query the sys_schemas table.
   • Workspace: Required if you are not querying the Workspaces table. This property is not required for querying the Workspaces table, as that query only returns a list of workspace slugs that can be used to set Workspace.

   Authenticating to Bitbucket

   Bitbucket supports OAuth authentication only. To enable this authentication from all OAuth flows, you must create a custom OAuth application, and set AuthScheme to OAuth.

   Be sure to review the Help documentation for the required connection properties for you specific authentication needs (desktop applications, web applications, and headless machines).

   Creating a custom OAuth application

   From your Bitbucket account:

   1. Go to Settings (the gear icon) and select Workspace Settings.
   2. In the Apps and Features section, select OAuth Consumers.
   3. Click Add Consumer.
   4. Enter a name and description for your custom application.
   5. Set the callback URL:
      • For desktop applications and headless machines, use http://localhost:33333 or another port number of your choice. The URI you set here becomes the CallbackURL property.
      • For web applications, set the callback URL to a trusted redirect URL. This URL is the web location the user returns to with the token that verifies that your application has been granted access.
   6. If you plan to use client credentials to authenticate, you must select This is a private consumer. In the driver, you must set AuthScheme to client.
   7. Select which permissions to give your OAuth application. These determine what data you can read and write with it.
   8. To save the new custom application, click Save.
   9. After the application has been saved, you can select it to view its settings. The application's Key and Secret are displayed. Record these for future use. You will use the Key to set the OAuthClientId and the Secret to set the OAuthClientSecret.

4. Configure the resource in the Web.xml:

    jdbc/bitbucketdb
    javax.sql.DataSource
    Container
   
   

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

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

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.