Configure the CData JDBC Driver for SAS xpt 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 SAS xpt data from a connection pool in Tomcat.

Connect to SAS xpt 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.

   Connecting to Local SASXpt Files

   You can connect to local SASXpt file by setting the URI to a folder containing SASXpt files.

   Connecting to S3 data source

   You can connect to Amazon S3 source to read SASXpt files. Set the following properties to connect:

   • URI: Set this to the folder within your bucket that you would like to connect to.
   • AWSAccessKey: Set this to your AWS account access key.
   • AWSSecretKey: Set this to your AWS account secret key.
   • TemporaryLocalFolder: Set this to the path, or URI, to the folder that is used to temporarily download SASXpt file(s).

   Connecting to Azure Data Lake Storage Gen2

   You can connect to ADLS Gen2 to read SASXpt files. Set the following properties to connect:

   • URI: Set this to the name of the file system and the name of the folder which contacts your SASXpt files.
   • AzureAccount: Set this to the name of the Azure Data Lake storage account.
   • AzureAccessKey: Set this to our Azure DataLakeStore Gen 2 storage account access key.
   • TemporaryLocalFolder: Set this to the path, or URI, to the folder that is used to temporarily download SASXpt file(s).

   Built-in Connection String Designer

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

   java -jar cdata.jdbc.sasxpt.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/sasxpt" auth="Container" type="javax.sql.DataSource" driverClassName="cdata.jdbc.sasxpt.SASXptDriver" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" url="jdbc:sasxpt:URI=C:/folder;" maxActive="20" maxIdle="10" maxWait="-1" />
   

   To allow a single application to access SAS xpt 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 SAS xpt for all applications.

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

    SAS xpt data JSP
    jdbc/SASXpt
    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/SASXpt");
   Connection conn = ds.getConnection();
    

More Tomcat Integration

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