Data source minimum required settings, by vendor

These properties vary according to the database vendor requirements for Java™ Database Connectivity (JDBC) driver implementations. You must set the appropriate properties on every data source that you configure.

Use these tables for quick reference on the JDBC providers that represent your JDBC driver classes. Each table corresponds to a specific database vendor, product, and platform.

Following the tables are links to detailed requirements for creating data sources that correspond to each JDBC provider that the application server supports . The list includes information about connection properties that are required by the database and any optional properties that the JDBC driver supports. Use the administrative console or the wsadmin scripting tool to define these properties on your data sources.

Table 1. Apache Derby JDBC providers. Use the table for quick reference on database-specific JDBC providers.
Apache Derby
JDBC provider	Transaction support	Version and other considerations
Derby JDBC Provider	One-phase	Does not support Version 4 data sources Configurable only in nodes at version 6.0.2 and later Not for use in clustered environment: accessible from a single JVM only
Derby JDBC Provider (XA)	One and two phase	Does not support Version 4 data sources Configurable only in nodes at version 6.0.2 and later Not for use in clustered environment: accessible from a single JVM only
Derby JDBC Provider 40	One-phase	Configurable only in nodes at version 7.0 and later Does not support Version 4 data sources
Derby JDBC Provider 40 (XA)	One and two phase	Configurable only in nodes at version 7.0 and later Does not support Version 4 data sources
Derby Network Server Using Derby Client	One-phase	Does not support Version 4.0 data sources. Configurable only in nodes at version 6.1 and later Can be used in clustered environment: a database instance can be accessed by multiple JVMs Only for use with Apache Derby databases that run on the same node as the application server
Derby Network Server Using Derby Client (XA)	One and two phase	Does not support Version 4 data sources Configurable only in nodes at version 6.1 and later Can be used in clustered environment: a database instance can be accessed by multiple JVMs Only for use with Apache Derby databases that run on the same node as the application server
Derby Network Server Using Derby Client 40	One-phase	Configurable only in nodes at version 7.0 and later Does not support Version 4 data sources
Derby Network Server Using Derby Client 40 (XA)	One and two phase	Configurable only in nodes at version 7.0 and later Does not support Version 4 data sources

Table 2. DB2 on AIX, HP-UX, Linux, Solaris, and Windows systems JDBC providers. Use the table for quick reference on database-specific JDBC providers.
DB2® on AIX®, HP-UX, Linux®, Solaris, and Windows systems
JDBC provider	Transaction support	Version and other considerations
DB2 Using IBM® JCC Driver	One-phase	Configurable in nodes that are at version 7.0 and later. Supports one-phase commit processing only, unless you use the application server on z/OS® with the type 2 JDBC driver. On the application server for z/OS, the type 2 JDBC driver uses RRS and supports two-phase commit processing.
DB2 Using IBM JCC Driver (XA)	One and two phase	Configurable in nodes that are at version 7.0 and later. Do not use the type 2 JDBC driver on the application server for z/OS.
DB2 Universal JDBC Provider	One-phase	N/A
DB2 Universal JDBC Provider (XA)	One and two phase	N/A

Table 3. DB2 UDB for iSeries JDBC providers. Use the table for quick reference on database-specific JDBC providers.
DB2 UDB for iSeries
JDBC provider	Transaction support	Version and other considerations
DB2 UDB for iSeries (Native)	One-phase	Recommended when you run the application server on iSeries.
DB2 UDB for iSeries (Native XA)	One and two phase	Recommended when you run the application server on iSeries.
DB2 UDB for iSeries (Toolbox)	One-phase	N/A
DB2 UDB for iSeries (Toolbox XA)	One and two phase	N/A
DB2 Universal JDBC Provider (XA)	One and two phase	Only for use when you run the application server on z/OS. Only driver type 4 is supported Does not support Version 4 data sources

Table 4. DB2 on z/OS JDBC providers. Use the table for quick reference on database-specific JDBC providers.
DB2 on z/OS
JDBC provider	Transaction support	Version and other considerations
DB2 Using IBM JCC Driver	One-phase	Configurable in version 7.0 and later nodes.
DB2 Using IBM JCC Driver (XA)	One and two phase	Configurable version 7.0 and later nodes.
DB2 Universal JDBC Provider	One-phase when connecting to the application server that is on AIX, HP-UX, Linux, Solaris, Windows, and iSeries systems One and two phase when you connect to the application server for z/OS with the type 2 JDBC driver.
DB2 Universal JDBC Provider (XA)	One and two phase

Table 5. Informix JDBC providers. Use the table for quick reference on database-specific JDBC providers.
Informix®
JDBC provider	Transaction support	Version and other considerations
Informix Using IBM JCC Driver	One phase	This provider is configurable in nodes that are at version 7.0 and later.
Informix Using IBM JCC Driver (XA)	One and two phase	This provider is configurable in nodes that are at version 7.0 and later.
Informix JDBC Driver	One-phase	N/A
Informix JDBC Driver (XA)	One and two phase	N/A
Informix using IBM DB2 JDBC Universal Driver	One phase	This provider is configurable in nodes that are at version 7.0 and later.
Informix using IBM DB2 JDBC Universal Driver (XA)	One and two phase	This provider is configurable in nodes that are at version 7.0 and later.

Table 6. Microsoft SQL Server JDBC providers. Use the table for quick reference on database-specific JDBC providers.
Microsoft SQL Server
JDBC provider	Transaction support	Version and other considerations
Microsoft SQL Server JDBC Driver	One-phase	N/A
Microsoft SQL Server JDBC Driver (XA)	One and two phase	N/A
DataDirect ConnectJDBC Provider type 4 driver for MS SQL Server	One-phase	N/A
DataDirect ConnectJDBC Provider, type 4 driver, for MS SQL Server (XA)	One and two phase	N/A

Table 7. Oracle JDBC providers. Use the table for quick reference on database-specific JDBC providers.
Oracle
JDBC provider	Transaction support	Version and other considerations
Oracle JDBC Driver	One-phase	Must use the ojdbc6.jar driver to connect to any version of Oracle database.
Oracle JDBC Driver(XA)	One and two phase	Must use the ojdbc6.jar driver to connect to any version of Oracle database.

Table 8. Sybase JDBC providers. Use the table for quick reference on database-specific JDBC providers.
Sybase
JDBC provider	Transaction support	Version and other considerations
Sybase JDBC 4 Driver	One-phase	jConnect v7.0
Sybase JDBC 4 Driver (XA)	One and two phase	jConnect v7.0
Sybase JDBC 3 Driver	One-phase	jConnect v6.05
Sybase JDBC 3 Driver (XA)	One and two phase	jConnect v6.05
Sybase JDBC 2 Driver	One-phase	jConnect v5.5
Sybase JDBC 2 Driver (XA)	One and two phase	jConnect v5.5
Deprecated feature: Support for Sybase jConnect 5.5 is deprecated. You might want to use a later provider that uses Sybase jConnect 6.05 or jConnect 7.0.

Detailed requirements

The following list identifies required class files and connection properties per JDBC provider.

After you determine the JDBC provider that suits your application and environment, ensure that you acquire the corresponding JDBC driver at a release level supported by this version of the application server. Consult the IBM support website for supported hardware and software.

Use the following links to navigate to the requirements list. Each link corresponds to a specific database vendor, product, and platform.

The WebSphere® Application Server detailed system requirements page lists versions of JDBC drivers and databases that have been tested and certified to work with each version of WebSphere Application Server. Newer versions of JDBC drivers and databases that did not exist when a version of WebSphere Application Server was in development might not be listed or be certified to work with WebSphere Application Server. In addition, other JDBC driver and database products that are not listed were not tested or certified.

WebSphere Application Server supports the use of any JDBC-compliant JDBC driver with the product. JDBC drivers and databases that were not tested and certified to work with WebSphere Application Server can still be used. User-defined JDBC Providers can be configured in the administrative console. You might be able to use these JDBC drivers with your applications without major issues. However, unexpected problems can occur since the drivers were not tested or certified. If you encounter a problem with a JDBC driver that has not been tested or certified, work with WebSphere Application Server support to troubleshoot the issue. If the support team does not find a problem that is specific to that JDBC driver or database, and it is not on the systems requirements page, a fix is not guaranteed. Use the JDBC drivers and databases that are listed on the system requirements page whenever possible.