The following list contains descriptions for every JDBC provider that can be defined for use with WebSphere Application Server Versions 5.x and 5.1.x. It also shows the supported data source classes and their required properties.
Specific fields are designated for the user and password properties. Inclusion of a property in the list does not imply that you should add it to the data source properties list. Rather, inclusion in the list means that a value is typically required for that field.
Use this list to find the provider information:
DB2
The DB2 Universal JDBC Driver is an architecture-neutral JDBC driver for distributed and local DB2 access. Because the Universal Driver architecture is independent of any particular JDBC driver connectivity or target platform, it allows both Java connectivity (Type 4) or Java Native Interface (JNI) based connectivity (Type 2) in a single driver instance to DB2. Starting with WebSphere Application Server Version 5.0.2, the product now supports both Type 2 and Type 4 JDBC drivers. To use the Type 4 driver, you must install DB2 Version 8.1 or a later version. To use the Type 2 driver, you must install DB2 Version 8.1 Fix Pack 2 or a later version.
This driver only supports one phase transactions. This JDBC driver allows applications to use both JDBC and Structured Query Language in Java (SQLJ) access.
The DB2 Universal JDBC Driver supports one phase data source:
com.ibm.db2.jcc.DB2ConnectionPoolDataSourceThe provider requires JDBC driver files:
Note: To find out the version of the universal driver you are using, issue this DB2 command:
java com.ibm.db2.jcc.DB2Jcc -versionThe output for the above example is:
IBM DB2 JDBC Universal Driver Architecture 1.5.xx
The db2jcc_license_cisuz.jar does not ship with Websphere Application Server and should be located in the same directory as the db2jcc.jar file, so that the DB2UNIVERSAL_JDBC_DRIVER_PATH points to both.
The classpath for this provider is set as follows: <classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar </classpath> <classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar</classpath> <classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cisuz.jar</classpath>Note: The license jar files are independent of each other; therefore, order does not matter.
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelperIf you use this provider to connect to DB2 for z/OS, you must change the data store helper class to:
com.ibm.websphere.rsadapter.DB2390DataStoreHelper
The driver requires a valid authentication alias.
It requires the following properties:
The DB2 Universal JDBC Driver (XA) is an architecture-neutral JDBC driver for distributed and local DB2 access. In WebSphere Application Server Version 5.0.2, this driver only supports Java Native Interface (JNI) based connectivity (Type 2) in a single driver instance to DB2. To use this driver, you must install DB2 Version 8.1 Fix Pack 2 or a later version. This driver supports two phase transactions and the WebSphere Application Server Version 5.0 data source. This driver allows applications to use both JDBC and SQLJ access.
The DB2 Universal JDBC Driver supports the two phase data source:
com.ibm.db2.jcc.DB2XADataSource
This provider requires JDBC driver files:
Note: To find the level of universal driver you are using, issue the following DB2 command:
java com.ibm.db2.jcc.DB2Jcc -versionexample output of the above:
IBM DB2 JDBC Universal Driver Architecture 1.5.xx
You must use the right license jar file to access a specific database backend.
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelperIf you use this provider to connect to DB2 for z/OS, you must change the data store helper class to:
com.ibm.websphere.rsadapter.DB2390DataStoreHelper
The driver requires a valid authentication alias.
It also requires the following properties:
The DB2 legacy CLI-based Type 2 JDBC Driver Provider is built on top of DB2 CLI (Call Level Interface). It uses the DB2 CLI interface to communicate with DB2 UDB servers.
DB2 legacy CLI-based Type 2 JDBC Driver supports one phase data source:
COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource
This provider requires JDBC driver files: db2java.zip (Note: If you run SQLJ in DB2 Version 8, db2jcc.jar is also required.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2DataStoreHelper
This driver does not require a valid authentication alias.
It requires the following properties:
The DB2 legacy CLI-based Type 2 JDBC Driver (XA) is built on top of DB2 CLI (Call Level Interface). It uses the DB2 CLI interface to communicate with DB2 UDB servers.
DB2 legacy CLI-based Type 2 JDBC Driver (XA) supports two phase data source:
COM.ibm.db2.jdbc.DB2XADataSource
This provider requires JDBC driver files: db2java.zip (Note: If you run SQLJ in DB2 Version 8, db2jcc.jar is also required.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2DataStoreHelper
This driver does not require a valid authentication alias.
It requires the following properties:
This JDBC provider is the same as the DB2 Legacy CLI-based Type 2 JDBC Driver. This JDBC driver is deprecated. Use the DB2 Legacy CLI-based Type 2 JDBC Driver instead of this one.
DB2 JDBC Provider supports one phase data source:
COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource
This provider requires JDBC driver files: db2java.zip (Note: If you run SQLJ in DB2 Version 8, db2jcc.jar is also required.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2DataStoreHelper
This driver does not require a valid authentication alias.
It requires the following properties:
This JDBC provider is the same as the DB2 Legacy CLI-based Type 2 JDBC Driver (XA). This JDBC driver is deprecated. Use the DB2 Legacy CLI-based Type 2 JDBC Driver (XA) instead of this one.
DB2 JDBC Provider (XA) supports two phase data source:
COM.ibm.db2.jdbc.DB2XADataSource
This provider requires JDBC driver files: db2java.zip (Note: If you run SQLJ in DB2 Version 8, db2jcc.jar is also required.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2DataStoreHelper
This driver does not require a valid authentication alias.
It requires the following properties:
For more information on DB2, visit the DB2 Web site at: http://www.ibm.com/software/data/db2/ .
For information on configuring WebSphere Application Server for DB2 access, see the Configuring DB2 article.
DB2 UDB for iSeries
The iSeries Developer Kit for Java contains this Type 2 JDBC driver that is built on top of the iSeries DB2 Call Level Interface (CLI) native libraries. Only use this driver for local DB2 connections on iSeries. It is not recommended for remote access. Use this driver for iSeries V5R2, or later releases.
DB2 UDB for iSeries (Native V5R2 and later) supports one phase data source:
com.ibm.db2.jdbc.app.UDBConnectionPoolDataSource
This provider requires JDBC driver files: db2_classes.jar
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper
It does not require an authentication alias.
This driver requires the following properties:
The iSeries Developer Kit for Java contains this XA-compliant Type 2 JDBC driver built on top of the iSeries DB2 Call Level Interface (CLI) native libraries. Only use this driver for local DB2 connections on iSeries. It is not recommended for remote access. Use this driver for iSeries V5R2 or later releases.
DB2 UDB for iSeries (Native XA - V5R2 and later) supports two phase data source:
com.ibm.db2.jdbc.app.UDBXADataSource
This provider requires JDBC driver files: db2_classes.jar
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper
It does not require an authentication alias.
This driver requires the following properties:
The iSeries Developer Kit for Java contains this Type 2 JDBC driver that is built on top of the iSeries DB2 Call Level Interface (CLI) native libraries. Only use this driver for local DB2 connections on iSeries. It is not recommended for remote access. Use this driver for iSeries V5R1, or earlier releases.
DB2 UDB for iSeries (Native V5R1 and earlier) supports one phase data source:
com.ibm.db2.jdbc.app.DB2StdConnectionPoolDataSource
This provider requires JDBC driver files: db2_classes.jar
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper
It does not require an authentication alias.
The driver requires the following properties:
The V5R1 and earlier JDBC drivers, although still supported, will receive no further enhancements. We recommend that you replace them with the V5R2 JDBC driver providers.
The iSeries Developer Kit for Java contains this XA-compliant Type 2 JDBC driver built on top of the iSeries DB2 Call Level Interface (CLI) native libraries. Only use this driver for local DB2 connections on iSeries. It is not recommended for remote access. Use this driver for iSeries V5R1, or earlier releases.
DB2 UDB for iSeries (Native XA - V5R1 and earlier) supports two phase data source:
com.ibm.db2.jdbc.app.DB2StdXADataSource
This provider requires JDBC driver files: db2_classes.jar
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper
It does not require an authentication alias.
This driver requires the following properties:
The V5R1 and earlier JDBC drivers, although still supported, will receive no further enhancements. We recommend that you replace them with the V5R2 JDBC driver providers.
This JDBC driver, also known as iSeries Toolbox driver for Java, is provided in the DB2 for iSeries database server. Use this driver for remote DB2 connections on iSeries. We recommend you use this driver instead of the IBM Developer Kit for Java JDBC Driver to access remote DB2 UDB for iSeries systems.
DB2 UDB for iSeries (Toolbox) supports one phase data source:
com.ibm.as400.access.AS400JDBCConnectionPoolDataSource
This provider requires JDBC driver files: jt400.jar
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper
This driver does not require an authentication alias if WebSphere Application Server and DB2 UDB for iSeries are installed in the same server. If they are installed in different servers, the user ID and password are required.
It requires the following properties:
This XA compliant JDBC driver, also known as iSeries Toolbox XA compliant driver for Java, is provided in the DB2 for iSeries database server. Use this driver for remote DB2 connections on iSeries. We recommend you use this driver instead of the IBM Developer Kit for Java JDBC Driver to access remote DB2 UDB for iSeries systems.
DB2 UDB for iSeries (Toolbox XA) supports two phase data source:
com.ibm.as400.access.AS400JDBCXADataSource
This provider requires JDBC driver files: jt400.jar
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper
This driver does not require an authentication alias if WebSphere Application Server and DB2 UDB for iSeries are installed in the same server. If they are installed in different servers, the user ID and password are required.
The driver requires the following properties:
For more information on DB2 UDB for iSeries, visit the DB2 Web site at: http://www.ibm.com/software/data/db2/
DB2 for z/OS
The DB2 for z/OS JDBC Provider provides remote JDBC access to DB2 on z/OS. This is the Legacy CLI-based JDBC driver. You cannot use this driver locally on DB2 z/OS. Use the DB2 for z/OS Local JDBC Provider (RRS) on local z/OS systems. You cannot see this JDBC Provider on the JDBC Provider drop down list in the administrative console. To create DB2 for z/OS data sources, use the DB2 Legacy CLI-based Type 2 JDBC Driver instead of this one, and change the DataStoreHelper class to com.ibm.websphere.rsadapter.DB2390DataStoreHelper.
DB2 for z/OS JDBC provider supports one phase data source:
COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource
This provider requires JDBC driver files: db2java.zip
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2390DataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
The DB2 for z/OS JDBC Provider provides remote XA-compliant JDBC access to DB2 on z/OS. You cannot use this driver locally on DB2 z/OS. Use the DB2 for z/OS Local JDBC Provider (RRS) on local z/OS systems. You cannot see this JDBC Provider on the JDBC Provider drop down list in the administrative console. To create DB2 for z/OS XA data sources, use the DB2 Legacy CLI-based Type 2 JDBC Driver (XA) instead of this one, and change the DataStoreHelper class to com.ibm.websphere.rsadapter.DB2390DataStoreHelper.
DB2 for z/OS JDBC (XA) provider supports two phase data source:
COM.ibm.db2.jdbc.DB2XADataSource
This provider requires JDBC driver files: db2java.zip
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2390DataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
The DB2 for z/OS Local JDBC Provider provides local JDBC access to DB2 on z/OS. This provider uses the native z/OS Resource Recovery Services (RRS) transaction manager to handle two-phase commit transactions. You cannot see this JDBC Provider on the JDBC Provider drop down list in the administrative console. This JDBC Provider is only used when accessing local databases in the z/OS system. Currently this JDBC Provider is only supported in WebSphere Application Server for z/OS.
DB2 for z/OS Local JDBC provider supports two phase data source:
COM.ibm.db2.jcc.DB2ConnectionPoolDataSource
This provider requires JDBC driver files: db2j2classes.zip
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.DB2390LocalDataStoreHelper
This driver does not require a valid authentication alias.
It requires the following properties:
For more information on DB2 for z/OS, visit the DB2 Web site at: http://www.ibm.com/software/data/db2/ .
Cloudscape
The Cloudscape JDBC Provider provides the JDBC access to the Cloudscape database. This Cloudscape JDBC driver used the embedded framework. You cannot use any Version 4.0 data sources with Cloudscape.
Cloudscape JDBC Provider supports one phase data source:
com.ibm.db2j.jdbc.DB2jConnectionPoolDataSource
This provider requires JDBC driver files: db2j.jar. (This file ships with WebSphere Application Server. If you are running Cloudscape Version 5.1, you can find this file in the WAS_HOME/cloudscape/lib directory).
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper
This driver does not require a valid authentication alias.
It requires the following properties:
The Cloudscape JDBC Provider (XA) provides the XA-compliant JDBC access to the Cloudscape database. This Cloudscape JDBC driver uses the embedded framework. You cannot use any Version 4.0 data sources with Cloudscape.
Cloudscape JDBC Provider (XA) supports two phase data source:
com.ibm.db2j.jdbc.DB2jXADataSource
This provider requires JDBC driver files: db2j.jar (This file ships with WebSphere Application Server. If you are running Cloudscape Version 5.1, you can find this file in the WAS_HOME/cloudscape/lib directory).
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper
This driver does not require a valid authentication alias.
It requires the following properties:
This Cloudscape driver takes advantage of the Network Server support that the DB2 universal Type 4 JDBC driver provides. You cannot use any Version 4.0 data sources with Cloudscape.
Cloudscape uses the DB2 Universal Driver when using the Network Server. It supports one phase data source:
com.ibm.db2.jcc.DB2ConnectionPoolDataSource
This provider requires JDBC driver files:
<classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar</classpath> <classpath>${CLOUDSCAPE_JDBC_DRIVER_PATH}/otherJars/db2jcc.jar</classpath> <classpath>${CLOUDSCAPE_JDBC_DRIVER_PATH}/db2j.jar</classpath> <classpath>${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar</classpath>which means that the db2jcc.jar from DB2 always takes precedence. Note that this also means that you must set the DB2 environment variable DB2UNIVERSAL_JDBC_DRIVER_PATH in WebSphere when you set up your DB2 datasource. This is instead of hard coding the path of the db2jcc.jar for DB2 datasources.
Note: UNIVERSAL_JDBC_DRIVER_PATHis a WebSphere environment variable that is already defined to the location in Websphere Application Server where the license jar file above is located, and will only be used if the DB2UNIVERSAL_JDBC_DRIVER_PATH is not set. DB2 users should ensure that DB2UNIVERSAL_JDBC_DRIVER_PATH is set to avoid loading multiple vesions of the db2jcc.jar file.
Note: DB2UNIVERSAL_JDBC_DRIVER_PATH is a WebSphere environment variable that you must set to point to the location of db2jcc.jar file (that comes with DB2). This variable is set only if you create a db2 provider. See the DB2 section for more information on the DB2UNIVERSAL_JDBC_DRIVER_PATH path variable.
Note: Cloudscape requires only db2jcc_license_c.jar; however, WebSphere Application Server uses db2jcc_license_cu.jar because this works for both DB2 UDB and Cloudscape.
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.CloudscapeNetworkServerDataStoreHelper
Note: The administrative console incorrectly lists the DB2UniversalDataStoreHelper as the default value for the DataStoreHelper class. You must change the default value to com.ibm.websphere.rsadapter.CloudscapeNetworkServerDataStoreHelper. Also change the custom properties, using the instructions in the customer property section.
This driver also requires a valid authentication alias.
It requires the following properties:
See the Cloudscape setup instructions for more information on configuring the Cloudscape Network Server.
For more information on IBM Cloudscape, visit the Cloudscape Web site at: http://www.ibm.com/software/data/cloudscape/
Informix
The Informix JDBC Driver is a Type 4 JDBC driver that provides JDBC access to the Informix database.
Informix JDBC Driver supports one phase data source:
com.informix.jdbcx.IfxConnectionPoolDataSource
This provider requires JDBC driver files:
ifxjdbc.jar ifxjdbcx.jar
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.InformixDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
The Informix JDBC Driver (XA) is a Type 4 JDBC driver that provides XA-compliant JDBC access to the Informix database.
Informix JDBC Driver (XA) supports two phase data source:
com.informix.jdbcx.IfxXADataSource
This provider requires JDBC driver files:
ifxjdbc.jar ifxjdbcx.jar
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.InformixDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
For more information on Informix, visit the Informix Web site at: http://www.ibm.com/software/data/informix/
Sybase
The Sybase JDBC Driver is a Type 4 JDBC driver that provides JDBC access to the Sybase database.
Sybase JDBC Driver supports one phase data source:
com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource
This provider requires JDBC driver files: jconn2.jar.
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.SybaseDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
The Sybase JDBC Driver (XA) is a Type 4 JDBC driver that provides XA-compliant JDBC access to the Sybase database.
Sybase JDBC Driver (XA) supports two phase data source:
com.sybase.jdbc2.jdbc.SybXADataSource
This provider requires JDBC driver files: jconn2.jar.
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.SybaseDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
This JDBC Driver provider is the same as Sybase JDBC Driver. This JDBC driver is deprecated. Use Sybase JDBC Driver instead of this one.
Sybase 12.0 JDBC Driver supports one phase data source:
com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource
This provider requires JDBC driver files: jconn2.jar.
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.SybaseDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
This JDBC Driver provider is the same as Sybase JDBC Driver (XA). This JDBC driver is deprecated. Use the Sybase JDBC Driver (XA) instead of this one.
Sybase 12.0 JDBC Driver (XA) supports two phase data source:
com.sybase.jdbc2.jdbc.SybXADataSource
This provider requires JDBC driver files: jconn2.jar.
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.SybaseDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
For more information on Sybase, visit the Sybase Web site at: http://www.sybase.com/
Oracle
The Oracle JDBC Driver provides JDBC access to the Oracle database. This JDBC driver supports both Type 2 JDBC access and Type 4 JDBC access.
Oracle JDBC Driver supports one phase data source:
oracle.jdbc.pool.OracleConnectionPoolDataSource
This provider requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.OracleDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
The Oracle JDBC Driver (XA) provides XA-compliant JDBC access to the Oracle database. This JDBC driver supports both Type 2 JDBC access and Type 4 JDBC access.
Oracle JDBC Driver (XA) supports two phase data source:
oracle.jdbc.xa.client.OracleXADataSource
This provider requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.OracleDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
Both the Oracle JDBC Thin Driver and the Oracle JDBC oci8 Driver are deprecated. Use the Oracle JDBC Driver instead of these two.
Oracle JDBC Thin Driver is a Type 4 JDBC driver that provides JDBC access to the Oracle database. Oracle JDBC Thin Driver is deprecated. Use the Oracle JDBC Driver instead of this one.
Oracle JDBC Thin Driver supports one phase data source:
oracle.jdbc.pool.OracleConnectionPoolDataSource
This provider requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.OracleDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
Both the Oracle JDBC Thin Driver (XA) and the Oracle JDBC oci8 Driver (XA) are deprecated. Use the Oracle JDBC Driver (XA) instead of these two.
Oracle JDBC Thin Driver (XA) is a Type 4 JDBC driver that provides XA-compliant JDBC access to the Oracle database. Oracle JDBC Thin Driver (XA) is deprecated. Use the Oracle JDBC Driver (XA) instead of this one.
Oracle JDBC Thin Driver (XA) supports two phase data source:
oracle.jdbc.xa.client.OracleXADataSource
This provider requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.OracleDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
Both the Oracle JDBC Thin Driver and the Oracle JDBC oci8 Driver are deprecated. Use the Oracle JDBC Driver instead of these two.
Oracle JDBC oci8 Driver is a Type 2 JDBC driver that provides JDBC access to the Oracle database. Oracle JDBC oci8 Driver is deprecated. Use the Oracle JDBC Driver instead of this one.
Oracle JDBC oci8 Driver supports one phase data source:
oracle.jdbc.pool.OracleConnectionPoolDataSource
This provider requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.OracleDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
Both the Oracle JDBC Thin Driver (XA) and the Oracle JDBC oci8 Driver (XA) are deprecated. Use the Oracle JDBC Driver (XA) instead of these two.
Oracle JDBC oci8 Driver (XA) is a Type 2 JDBC driver that provides XA-compliant JDBC access to the Oracle database. Oracle JDBC oci8 Driver (XA) is deprecated. Use the Oracle JDBC Driver (XA) instead of this one.
Oracle JDBC oci8 Driver (XA) supports two phase data source:
oracle.jdbc.xa.client.OracleXADataSource
This provider requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.OracleDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
For more information on Oracle, visit the Oracle Web site at: http://www.oracle.com/
MS SQL Server
DataDirect ConnectJDBC type 4 driver for MS SQL Server is a Type 4 JDBC driver that provides JDBC access to the MS SQL Server database. This provider is for use only with the ConnectJDBC driver purchased from DataDirect Technologies.
This JDBC provider supports this data source:
com.ddtek.jdbcx.sqlserver.SQLServerDataSource
It requires JDBC driver files:
sqlserver.jar, base.jar and util.jar(The spy.jar file is optional. You need this file to enable spy logging. The spy.jar file is not in the same directory as the other three jar files. Instead, it is located in the ../spy/ directory.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
DataDirect ConnectJDBC type 4 driver for MS SQL Server (XA) is a Type 4 JDBC driver which provides XA-compliant JDBC access to the MS SQL Server database. This provider is for use only with the ConnectJDBC driver purchased from DataDirect Technologies.
This JDBC provider supports this data source:
com.ddtek.jdbcx.sqlserver.SQLServerDataSource.
It requires JDBC driver files:
sqlserver.jar, base.jar and util.jar.(The spy.jar file is optional. You need this file to enable spy logging. The spy.jar file is not in the same directory as the other three jar files. Instead, it is located in the ../spy/ directory.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
For more information on the DataDirect ConnectJDBC driver, visit the DataDirect Web site at: http://www.datadirect-technologies.com/
WebSphere embedded ConnectJDBC driver for MS SQL Server is a Type 4 JDBC driver that provides JDBC access to the MS SQL Server database. This JDBC driver ships with WebSphere Application Server. Only use this provider with the Connect JDBC driver embedded in WebSphere; it cannot be used with a Connect JDBC driver purchased separately from DataDirect Technologies.
This JDBC provider supports this data source:
com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource.
This provider requires JDBC driver files:
sqlserver.jar base.jar and util.jar.(The spy.jar file is optional. You need this file to enable spy logging. The spy.jar file for the WebSphere embedded Connect JDBC driver ships with WebSphere Application Server. All the files are located in the WAS_HOME/lib/ directory.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.WSConnectJDBCDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
WebSphere embedded ConnectJDBC driver for MS SQL Server (XA) is a Type 4 JDBC driver which provides XA-compaint JDBC access to the MS SQL Server database. This JDBC driver ships with WebSphere Application Server. Use this provider with the Connect JDBC driver embedded in WebSphere. Do not use it with a Connect JDBC driver purchased separately from DataDirect Technologies.
This JDBC provider supports this data source:
com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource.
This provider requires JDBC driver files:
sqlserver.jar base.jar and util.jar.(The spy.jar file is optional. You need this file to enable spy logging. The spy.jar file for the WebSphere embedded Connect JDBC driver ships with WebSphere Application Server. All the files are located in the WAS_HOME/lib/ directory.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.WSConnectJDBCDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
To view the instructions for installing Stored Procedures for JTA (required when enabling two-phase commit) on the WebSphere CD, refer to the following FTP site:
How to install "Stored Procedures for JTA" from the WebSphere CD
You can download the latest patches and upgrades to the WebSphere embedded ConnectJDBC drivers from the following FTP site:
ftp://ftp.software.ibm.com/software/websphere/info/tools/DataDirect/datadirect.htm
DataDirect SequeLink type 3 JDBC driver for MS SQL Server is a type 3 JDBC driver that provides JDBC access to MS SQL Server via SequeLink server. This JDBC driver provider is for use only with the SequelLink type 3 JDBC driver purchased from DataDirect Technologies.
This JDBC provider supports the data source:
com.ddtek.jdbcx.sequelink.SequeLinkDataSource
This provider requires JDBC driver files:
sljc.jar and spy-sl53.jar(The JDBC driver shipped with WebSphere Application Server requires the sljc.jar and the spy-sl53.jar files. The JDBC driver purchased from DataDirect requires the sljc.jar and the spy.jar files. The spy.jar and spy-sl35.jar files are optional. You need these files to enable spy logging.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.SequeLinkDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
DataDirect SequeLink type 3 JDBC driver for MS SQL Server (XA) is a type 3 JDBC driver that provides XA-compliant JDBC access to MS SQL Server via the SequeLink server. This JDBC driver provider is for use only with the SequelLink type 3 JDBC driver purchased from DataDirect Technologies
This JDBC provider supports the data source:
com.ddtek.jdbcx.sequelink.SequeLinkDataSource
This provider requires JDBC driver files:
sljc.jar and spy-sl53.jar(The JDBC driver shipped with WebSphere Application Server requires the sljc.jar and the spy-sl53.jar files. The JDBC driver purchased from DataDirect requires the sljc.jar and the spy.jar files. The spy.jar and spy-sl35.jar files are optional. You need these files to enable spy logging.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.SequeLinkDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
To view instructions for installing SequeLink Server from the WebSphere CD, refer to this FTP site:
How to install SequeLink Server from the WebSphere CDOnly install the SequeLink server from the WebSphere CD if you are using the SequeLink JDBC driver embedded in WebSphere. Otherwise, install the SequeLink server purchased from DataDirect Technologies.
You can download the latest patches and upgrades to the WebSphere embedded SequeLink type 3 JDBC drivers from the following FTP site:
ftp://ftp.software.ibm.com/software/websphere/info/tools/DataDirect/datadirect.htm
For more information on the DataDirect SequeLink type 3 JDBC driver, visit the DataDirect Web site at:
http://www.datadirect-technologies.com/
Microsoft JDBC driver for MSSQLServer 2000 is a type 4 JDBC driver that provides JDBC access to the MS SQL Server database.
This JDBC provider supports this data source:
com.microsoft.jdbcx.sqlserver.SQLServerDataSource
This provider requires JDBC driver files:
mssqlserver.jar, msbase.jar and msutil.jar(The spy.jar file is optional. You need it to enable spy logging. However, Microsoft does not ship the spy.jar file. Contact Microsoft about this issue.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
Microsoft JDBC driver for MSSQLServer 2000 (XA) is a type 4 JDBC driver that provides XA-compaint JDBC access to the MS SQL Server database.
This JDBC provider supports this data source:
com.microsoft.jdbcx.sqlserver.SQLServerDataSource
This provider requires JDBC driver files:
mssqlserver.jar, msbase.jar and msutil.jar(The spy.jar file is optional. You need it to enable spy logging. However, Microsoft does not ship the spy.jar file. Contact Microsoft about this issue.)
The driver requires DataStoreHelper class:
com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper
It also requires a valid authentication alias.
This driver requires the following properties:
For more information on the Microsoft JDBC driver, visit the Microsoft Web site at:
http://www.microsoft.com/sql