Ready to get started?

Download a free trial of the AlloyDB Driver to get started:

 Download Now

Learn more:

AlloyDB Icon AlloyDB JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with AlloyDB.

Connect to AlloyDB Data from a Connection Pool in Jetty

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

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

    <Configure id='alloydbdemo' class="org.eclipse.jetty.webapp.WebAppContext"> <New id="alloydbdemo" class=""> <Arg><Ref refid="alloydbdemo"/></Arg> <Arg>jdbc/alloydbdb</Arg> <Arg> <New class="cdata.jdbc.alloydb.AlloyDBDriver"> <Set name="url">jdbc:alloydb:</Set> <Set name="User">alloydb</Set> <Set name="Password">admin</Set> <Set name="Database">alloydb</Set> <Set name="Server"></Set> <Set name="Port">5432</Set> </New> </Arg> </New> </Configure>

    The following connection properties are usually required in order to connect to AlloyDB.

    • Server: The host name or IP of the server hosting the AlloyDB database.
    • User: The user which will be used to authenticate with the AlloyDB server.
    • Password: The password which will be used to authenticate with the AlloyDB server.

    You can also optionally set the following:

    • Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
    • Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.

    Authenticating with Standard Authentication

    Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.

    No further action is required to leverage Standard Authentication to connect.

    Authenticating with pg_hba.conf Auth Schemes

    There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.

    Find instructions about authentication setup on the AlloyDB Server here.

    Authenticating with MD5 Authentication

    This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.

    Authenticating with SASL Authentication

    This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.

    Authenticating with Kerberos

    The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos.

  4. Configure the resource in the Web.xml:

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

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.