Configure the CData JDBC Driver for EnterpriseDB in a Connection Pool in Tomcat

The CData JDBC Drivers support standard JDBC interfaces to integrate with Web applications running on the JVM. This article details how to connect to EnterpriseDB data from a connection pool in Tomcat.

Connect to EnterpriseDB Data through a Connection Pool in Tomcat

1. Copy the CData JAR and CData .lic file to $CATALINA_HOME/lib. The CData JAR is located in the lib subfolder of the installation directory.
2. Add a definition of the resource to the context. Specify the JDBC URL here.

   The following connection properties are required in order to connect to data.

   • Server: The host name or IP of the server hosting the EnterpriseDB database.
   • Port: The port of the server hosting the EnterpriseDB database.

   You can also optionally set the following:

   • Database: The default database to connect to when connecting to the EnterpriseDB Server. If this is not set, the user's default database will be used.

   Connect Using Standard Authentication

   To authenticate using standard authentication, set the following:

   • User: The user which will be used to authenticate with the EnterpriseDB server.
   • Password: The password which will be used to authenticate with the EnterpriseDB server.

   Connect Using SSL Authentication

   You can leverage SSL authentication to connect to EnterpriseDB data via a secure session. Configure the following connection properties to connect to data:

   • SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
   • SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
   • SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
   • SSLClientCertType: The certificate type of the client store.
   • SSLServerCert: The certificate to be accepted from the server.

   Built-in Connection String Designer

   For assistance in constructing the JDBC URL, use the connection string designer built into the EnterpriseDB JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

   java -jar cdata.jdbc.enterprisedb.jar
   

   Fill in the connection properties and copy the connection string to the clipboard.

   👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
   

   You can see the JDBC URL specified in the resource definition below.

   <Resource name="jdbc/enterprisedb" auth="Container" type="javax.sql.DataSource" driverClassName="cdata.jdbc.enterprisedb.EnterpriseDBDriver" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" url="jdbc:enterprisedb:User=postgres;Password=admin;Database=postgres;Server=127.0.0.1;Port=5444" maxActive="20" maxIdle="10" maxWait="-1" />
   

   To allow a single application to access EnterpriseDB data, add the code above to the context.xml in the application's META-INF directory.

   For a shared resource configuration, add the code above to the context.xml located in $CATALINA_BASE/conf. A shared resource configuration provides connectivity to EnterpriseDB for all applications.

3. Add a reference to the resource to the web.xml for the application.

    EnterpriseDB data JSP
    jdbc/EnterpriseDB
    javax.sql.DataSource
    Container
   
   

4. Initialize connections from the connection pool:

   Context initContext = new InitialContext();
   Context envContext = (Context)initContext.lookup("java:/comp/env");
   DataSource ds = (DataSource)envContext.lookup("jdbc/EnterpriseDB");
   Connection conn = ds.getConnection();
    

More Tomcat Integration

The steps above show how to connect to EnterpriseDB data in a simple connection pooling scenario. For more use cases and information, see the JNDI Datasource How-To in the Tomcat documentation.