Operating Systems: i5/OS
             Personalize the table of contents and search results

 

Data source minimum required settings, by vendor

 

These properties vary according to the database vendor requirements for JDBC driver implementations. 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 Vand other considerations
DB2 Universal JDBC Provider One phase only  
DB2 Universal JDBC Provider (XA) One and two phase  

DB2 UDB for iSeries
JDBC provider Transaction support Vand other considerations
DB2 UDB for iSeries (Native) One phase only

Recommended for use with WebSphere Application Server run on iSeries

DB2 UDB for iSeries (Native XA) One and two phase

Recommended for use with WebSphere Application Server run on iSeries

DB2 UDB for iSeries (Toolbox) One phase only  
DB2 UDB for iSeries (Toolbox XA) One and two phase  

DB2 on z/OS
JDBC provider Transaction support Vand other considerations
DB2 Universal JDBC Provider

  • One phase only when connecting to WebSphere Application Server run on Windows, supported UNIX systems, or supported Linux systems

  • One and two phase when connecting to WebSphere Application Server for the z/OS platform, using driver type 2

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

  • In WebSphere Application Server run on z/OS, you cannot use driver type 2 with the XA provider; in this case, use only driver type 4.

  • Does not support V4 data sources in WebSphere Application Server run on z/OS

Cloudscape V10.0Cloudscape V10.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: V10.0 cannot be used as a production database. V10.0 can only be used for development and test purposes.
JDBC provider Transaction support Vand other considerations

Derby JDBC Provider

One phase only

  • Not for use in clustered environment: accessible from a single JVM only

  • Does not support V4 data sources

Derby JDBC Provider (XA)

One and two phase

  • Not for use in clustered environment: accessible from a single JVM only

  • Does not support V4 data sources

Derby Network Server Provider using the Universal JDBC driver

One phase only

  • Can be used in clustered environment: a database instance can be accessed by multiple JVMs

  • Does not support XA

  • Does not support V4 data sources

Cloudscape V10.1.xBecause the Cloudscape v10.1.x code base is the product of the Open Source Apache Derby Project, Cloudscape v10.1.x uses Derby JDBC classes. Restriction: Version 10.1 cannot be used as a production database. V10.1 can only be used for development and test purposes.
JDBC provider Transaction support Vand other considerations

Derby JDBC Provider

One phase only

  • Not for use in clustered environment: accessible from a single JVM only

  • Does not support V4 data sources

Derby JDBC Provider (XA)

One and two phase

  • Not for use in clustered environment: accessible from a single JVM only

  • Does not support V4 data sources

Derby Network Server Provider using the Universal JDBC driver

Deprecated in WebSphere Application Server v.6.1

One phase only

  • Can be used in clustered environment: a database instance can be accessed by multiple JVMs

  • Does not support XA

  • Does not support V4 data sources

Derby Network Server using Derby Client provider

One phase only

  • Can be used in clustered environment: a database instance can be accessed by multiple JVMs

  • Does not support V4 data sources

  • Only for use with Cloudscape 10.1.x databases that run on the same node as WebSphere Application Server

Derby Network Server using Derby Client provider (XA)

One and two phase

  • Can be used in clustered environment: a database instance can be accessed by multiple JVMs

  • Does not support V4 data sources

  • Only for use with Cloudscape 10.1.x databases that run on the same node as WebSphere Application Server

Informix
JDBC provider Transaction support Vand other considerations
Informix JDBC Provider One phase only  
Informix JDBC Provider (XA) One and two phase  

Sybase
JDBC provider Transaction support Vand 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 Vand other considerations
Oracle JDBC Provider One phase only  
Oracle JDBC Provider(XA) One and two phase  

Microsoft SQL Server
JDBC provider Transaction support Vand other considerations
DataDirect ConnectJDBC Provider, type 4 driver, for MS SQL Server One phase only

  • Only for use with the corresponding driver from DataDirect Technologies

  • V3.5, Service pack 2 of the DataDirect ConnectJDBC type 4 driver can support access to both MS SQL Server 2005 and MS SQL Server 2000

DataDirect ConnectJDBC Provider, type 4 driver, for MS SQL Server (XA) One and two phase

  • Only for use with the corresponding driver from DataDirect Technologies

  • V3.5, Service pack 2 of the DataDirect ConnectJDBC type 4 driver can support access to both MS SQL Server 2005 and MS SQL Server 2000

IBM WebSphere embedded ConnectJDBC Provider for MS SQL Server One phase only

  • Cannot be used outside of WebSphere Application Server environment

  • V3.5, Service pack 2 of the driver can support access to both MS SQL Server 2005 and MS SQL Server 2000

IBM WebSphere embedded ConnectJDBC Provider for MS SQL Server (XA) One and two phase

  • Cannot be used outside of WebSphere Application Server environment

  • V3.5, Service pack 2 of the driver can support access to both MS SQL Server 2005 and MS SQL Server 2000

 

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 WebSphere Application Server. Consult the IBM support website for Application Server 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.




Sub-topics


Data source minimum required settings for DB2 UDB

Data source minimum required settings for Cloudscape

Data source minimum required settings for Informix

Data source minimum required settings for MS SQL Server

Data source minimum required settings for Oracle

Data source minimum required settings for Sybase

 

Related concepts


Data sources
Resource adapters
JDBC providers

 

Related tasks


Configuring a JDBC provider and data source
Configuring a JDBC provider using the administrative console
Configuring a data source using the administrative console
Creating and configuring a JDBC provider and data source using the Java Management Extensions API

 

Related information


WebSphere Application Server Supported hardware and software
DB2 product Web pages
DB2 for z/OS product Web pages
Information Management Software for z/OS Solutions Information Center

 

Reference topic