These properties vary according to the database vendor requirements for 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 supported JDBC provider. The list includes information about connection properties that database vendors require, as well as supported optional properties. Using either the administrative console or the wsadmin scripting tool, define these properties on your data sources.
DB2 on Windows, supported UNIX systems, or supported Linux systems | ||
---|---|---|
JDBC provider | Transaction support | Version and other considerations |
DB2 Universal JDBC Provider | One phase only | |
DB2 Universal JDBC Provider (XA) | One and two phase | |
DB2 legacy CLI-based Type 2 JDBC Provider | One phase only | |
DB2 legacy CLI-based Type 2 JDBC Provider (XA) | One and two phase |
DB2 on z/OS | ||
---|---|---|
JDBC provider | Transaction support | Version and other considerations |
DB2 for z/OS Local JDBC Provider (RRS), using the Legacy DB2 for OS/390 and z/OS JDBC Driver | One and two phase | Only for use with WebSphere Application Server run on z/OS |
DB2 Universal JDBC Provider |
|
WebSphere Application Server for the z/OS platform only: For two-phase transaction support, use driver type 2. Application Server then uses RRS to coordinate transaction processing. |
DB2 Universal JDBC Provider (XA) | One and two phase |
|
Cloudscape Version 5.1.60.x | ||
---|---|---|
JDBC provider | Transaction support | Version and other considerations |
Cloudscape JDBC Provider | One phase only |
|
Cloudscape JDBC Provider (XA) | One and two phase |
|
Cloudscape Network Server Provider using the Universal JDBC driver | One phase only |
|
Cloudscape Version 10.0 Cloudscape
Version 10.0 was formerly known as Derby. Because the new Cloudscape code
base is the product of the Open Source Apache Derby Project, Cloudscape v10.0
uses Derby JDBC classes.
Restriction: Version 10.0 cannot be used
as a production database. Version 10.0 can only be used for development
and test purposes.
|
||
---|---|---|
JDBC provider | Transaction support | Version and other considerations |
Derby JDBC Provider |
One phase only |
|
Derby JDBC Provider (XA) |
One and two phase |
|
Derby Network Server Provider using the Universal JDBC driver |
One phase only |
|
Informix | ||
---|---|---|
JDBC provider | Transaction support | Version and other considerations |
Informix JDBC Provider | One phase only | |
Informix JDBC Provider (XA) | One and two phase |
Sybase | ||
---|---|---|
JDBC provider | Transaction support | Version and other considerations |
Sybase jConnect for JDBC Provider | One phase only | |
Sybase jConnect for JDBC Provider (XA) | One and two phase |
Oracle | ||
---|---|---|
JDBC provider | Transaction support | Version and other considerations |
Oracle JDBC Provider | One phase only | |
Oracle JDBC Provider(XA) | One and two phase |
Microsoft SQL Server | ||
---|---|---|
JDBC provider | Transaction support | Version and other considerations |
DataDirect ConnectJDBC Provider, type 4 driver, for MS SQL Server | One phase only |
|
DataDirect ConnectJDBC Provider, type 4 driver, for MS SQL Server (XA) | One and two phase |
|
IBM WebSphere embedded ConnectJDBC Provider for MS SQL Server | One phase only |
|
IBM WebSphere embedded ConnectJDBC Provider for MS SQL Server (XA) | One and two phase |
|
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 WebSphere Application Server. Consult the IBM support website for Application Server supported hardware and software.