To connect MS Access to Tomcat, you need a JDBC driver. Although Microsoft do not produce a JDBC driver for Access, Easysoft provide two Microsoft Access JDBC drivers. Use these JDBC drivers to connect JSP pages and servlets running under Tomcat to Microsoft Access.

Binary JAR file downloads of the JDBC driver are available here and the current version with Maven Repository. Because Java is platform neutral, it is a simple process of just downloading the appropriate JAR file and dropping it into your classpath. Source versions are also available here for recent driver versions. Apache Tomcat 10.0.2 download page. Apache Tomcat Size: 11.6Mb. Downloaded: 7,417 times. I want to know if it is possible to use this JDBC driver with Tomcat 7. If so, how do I input the server.xml, web.xml(WEB-INF), and context.xml(WEB-INF)? Here is my context. Apache Tomcat is next to Apache's HTTP server, the second most successful technology the foundation is developing and curating. The Java Servlet and JavaServer Pages are technologies used in rendering Java-based web pages, and while many think they are a standard, you can still implement different ways how these technologies are run. Download the driver you need by visiting the DB2 Fix Packs by Version page or the IBM Data Server Client Packages fix pack page, which contain links to all available Fix Packs The following command will retrieve the JCC driver version if executed from the command line: java com.ibm.db2.jcc.DB2Jcc -version; Or for drivers that are not yet installed.

Download MS Access JDBC driver for Tomcat on Windows
The Easysoft JDBC-Access Driver connects Tomcat web apps running on Windows to local MS Access databases. For more information, see the JDBC-Access Driver Getting Started Guide.
Download MS Access JDBC driver for Tomcat on Linux and Unix
The JDBC-ODBC Bridge connects Tomcat web apps running on Linux or Unix to remote MS Access databases. For more information, see this tutorial.

Introduction

Apache Tomcat is a Java Servlet/JavaServer Pages (JSP) container that provides a platform for developing and deploying web applications and web services. Many web applications need to access a database through a JDBC driver and Tomcat makes a JDBC DataSource implementation available for this purpose. If your web application needs to access a database for which only an ODBC driver is either available or suitable, a JDBC-ODBC Bridge is required. Sun provide a JDBC-ODBC Bridge, however this driver is not recommended for use with Tomcat. The Apache Tomcat Database FAQ contains the following entry about the Sun JDBC-ODBC Bridge:

Do not use JDBC-ODBC bridge bundled with Sun’s JDK with Tomcat. It was never meant for a production server environment. If you ask a question about it, everyone will tell you to not use it. If you do need to use ODBC, there are 3rd party drivers which do a pretty good job at being thread safe.

The Easysoft JDBC-ODBC Bridge (JOB) is a thread-safe JDBC-ODBC driver that our customers use in production environments. JOB is compatible with Tomcat and allows Tomcat applications to access any database for which an ODBC driver is available. For example, use JOB to connect web applications running under Tomcat to a Microsoft Access database.

Installing the Easysoft JDBC-ODBC Bridge

If you have not already done so, please register with us to download a fully functional trial version of JOB.

Download, install and license the JOB Server for your database platform. For example, to connect to a Microsoft Access database, download the Windows JOB Server. On the machine where the JOB Server is running, configure an ODBC data source for the database you want to access. Test the data source with an ODBC application. Use one of the test applets included in the JOB distribution to check that you can access the ODBC data source through JOB.

For information about installing, licensing and testing JOB, refer to the Installation and Configuration chapters of the JOB User Guide.

Installing Apache Tomcat

When testing Apache Tomcat with JOB, we used:

Tomcat 7.0.19 with the J2SE Runtime Environment (JRE) 6 on Ubuntu Linux.
Tomcat 5.5.17 with the JRE 5.0 on Red Hat Linux.

Note This article follows the Apache Tomcat documentation convention of using $CATALINA_HOME to represent the root of the Tomcat installation directory. For example, if you install Tomcat 7.0.19 in /usr/local, $CATALINA_HOME represents /usr/local/apache-tomcat-7.0.19.

Apache Tomcat Prerequisites

Tomcat 7 requires JRE version 6.0 or later.

We downloaded the JRE 6 Update 26 Linux Self Extracting Installer from:

By default, Tomcat 5.5 requires JRE version 5.0 or later. However, Tomcat can be configured to run on earlier versions of the JRE. Refer to $CATALINA_HOME/RUNNING.txt if this is a requirement.

We downloaded the JRE 5.0 Linux RPM from:

To install the JRE, set execute permission on the .bin file and then run the binary. For example:

Installing and Running Apache Tomcat

Download the Core binary distribution from:
cd to the directory where you want to install Tomcat and unpack the Core binary distribution. For example:
Set the JAVA_HOME environment variable to the JRE directory path and export JAVA_HOME. For example:
Refer to $CATALINA_HOME/RELEASE-NOTES for information about any other environment variables you need to set for your platform.
Start Tomcat:
If you unpacked the Tomcat distribution into a directory that only root has write permission to, you need to run startup.sh as root. Download stmicroelectronics others driver.
If the Tomcat server is unable to start, the default Tomcat port 8080 may already be in use. Refer to the 'Troubleshooting' section in $CATALINA_HOME/RUNNING.txt for information about how to solve this and other common Tomcat installation problems.
In a web browser, go to the Tomcat home page at:
http://localhost:8080
If your web browser is not running on the same server as Tomcat, use this URL: http://tomcathost:8080. Replace tomcathost with the host name or IP address of the Tomcat server.
Test Tomcat by running the example web applications (available from the Examples section of the Tomcat home page.)

Installing the JOB JDBC Driver

To make JOB available to Tomcat’s internal classes and your web applications, copy the JOB client (EJOB.jar) to $CATALINA_HOME/common/lib.

On Windows, EJOB.jar is located in C:Program FilesEasysoftEasysoft JDBC-ODBC Bridgejars, by default. On Unix, EJOB.jar is located in installation_directory/easysoft/job/jars where installation_directory is the Easysoft installation directory, by default, /usr/local.

Adding JDBC Data Sources

To enable a web application to access an ODBC database through JOB, you need to create a JDBC data source. The JDBC data source needs to specify the JOB JDBC driver class, easysoft.sql.jobDriver, and a JOB connection URL that accesses the target ODBC data source. Note that you do not need to copy the JOB JDBC driver to your application’s WEB-INF/lib directory. The Tomcat server manages JDBC connections for web applications and will load the JOB driver from $CATALINA_HOME/common/lib.

JDBC data sources can be created as a web application resource or a global resource. Web application resources are only available to the application in whose context they are defined. Global resources can be used by multiple applications.

To add a JDBC data source as a web application resource, create a Resource entry in the application’s context.xml file.

To use the JDBC data source, your application needs to do a Java Naming and Directory Interface (JNDI) lookup on the data source name defined in the Resource entry (for example, jdbc/MyDB). All resources are placed in the java:comp/env portion of the JNDI namespace, so to access a JDBC data source, an application would do a JNDI lookup similar to the following:

Note that if you use Tomcat 5.0 or earlier, you also need to declare the JNDI name for the data source in the application’s WEB-INF/web.xml file. For example context.xml and web.xml entries, see Developing and Deploying the Web Application in the Sample Easysoft JDBC-ODBC Bridge Web Application section.

Global resources are outside of a Web application’s context. Resource links are used to make global resources available to a web application. To access a JDBC data source defined as a global resource, an application needs to do a JNDI lookup on the resource link name rather than the data source name.

Tomcat Driver Download