Data source minimum required settings, by vendor
Use these tables for quick reference on the JDBC providers that represent the JDBC driver classes.
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 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 the data sources.
| 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. |
| 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 |
|
| DB2 Using IBM JCC Driver (XA) | One and two phase |
|
| DB2 Universal JDBC Provider | One-phase | N/A |
| DB2 Universal JDBC Provider (XA) | One and two phase | N/A |
| DB2 UDB for iSeries | ||
|---|---|---|
| JDBC provider | Transaction support | Version and other considerations |
| (iSeries) DB2 UDB for iSeries (Native) | (iSeries) One-phase | (iSeries) Recommended when running the application server on iSeries. |
| (iSeries) DB2 UDB for iSeries (Native XA) | (iSeries) One and two phase | (iSeries) Recommended when running 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 |
| (ZOS) DB2 Universal JDBC Provider (XA) | (ZOS) One and two phase | (ZOS)
|
| 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
(ZOS) 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 | |
| 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. |
| 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 |
| 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. |
| 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. We might want to use a later provider that uses Sybase jConnect 6.05 or jConnect 7.0.depfeat
Detailed requirements
The following list identifies required class files and connection properties per JDBC provider.
After you determine the JDBC provider that suits the 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.
- Data source minimum required settings for Apache Derby
- DB2, connecting to the application server on AIX, HP-UX, Linux, Solaris, or Windows
- DB2 on z/OS, connecting to the application server on z/OS
- DB2 Universal Database for iSeries
- DB2 UDB for iSeries, connecting to the application server on z/OS
- Informix
- Microsoft SQL Server
- Oracle
- Sybase
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 WAS. Newer versions of JDBC drivers and databases that did not exist when a version of WAS was in development might not be listed or be certified to work with WAS. In addition, other JDBC driver and database products that are not listed were not tested or certified.
WAS 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 WAS can still be used. User-defined JDBC Providers can be configured in the administrative console. We might be able to use these JDBC drivers with the applications without major issues. However, unexpected problems can occur since the drivers were not tested or certified. If we encounter a problem with a JDBC driver with not been tested or certified, work with WAS 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 listed on the system requirements page whenever possible.
Related: