Connect to GitLab Data from a Connection Pool in Jetty
The CData JDBC driver for GitLab is easy to integrate with Java Web applications. This article shows how to efficiently connect to GitLab data in Jetty by configuring the driver for connection pooling. You will configure a JNDI resource for GitLab in Jetty.
Configure the JDBC Driver for Salesforce as a JNDI Data Source
Follow the steps below to connect to Salesforce from Jetty.
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
- Add the CData and license file, located in the lib subfolder of the installation directory, into the lib subfolder of the context path.
-
Declare the resource and its scope. Enter the required connection properties in the resource declaration. This example declares the GitLab data source at the level of the Web app, in WEB-INF\jetty-env.xml.
<Configure id='gitlabdemo' class="org.eclipse.jetty.webapp.WebAppContext"> <New id="gitlabdemo" class="org.eclipse.jetty.plus.jndi.Resource"> <Arg><Ref refid="gitlabdemo"/></Arg> <Arg>jdbc/gitlabdb</Arg> <Arg> <New class="cdata.jdbc.api.APIDriver"> <Set name="url">jdbc:api:</Set> <Set name="Profile">C:\profiles\GitLab.apip</Set> <Set name="ProfileSettings">'APIKey</Set> </New> </Arg> </New> </Configure>Start by setting the Profile connection property to the location of the GitLab Profile on disk (e.g. C:\profiles\GitLab.apip). Next, set the ProfileSettings connection property to the connection string for GitLab (see below).
GitLab API Profile Settings
Create a Personal Access Token in GitLab under User Settings > Access Tokens, selecting the required scopes (e.g.,
read_api
,api
). -
Configure the resource in the Web.xml:
jdbc/gitlabdb javax.sql.DataSource Container
-
You can then access GitLab with a lookup to java:comp/env/jdbc/gitlabdb:
InitialContext ctx = new InitialContext(); DataSource mygitlab = (DataSource)ctx.lookup("java:comp/env/jdbc/gitlabdb");
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.