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 is a list of 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 UDB for iSeries | ||
---|---|---|
JDBC provider | Transaction support | Version and other considerations |
DB2 UDB for iSeries (Toolbox) | One phase only | |
DB2 UDB for iSeries (Toolbox 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 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 |
|
DB2 legacy CLI-based Type 2 JDBC Provider | One phase only |
|
DB2 legacy CLI-based Type 2 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 |
|
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 WebSphere Application Server prerequisite Web site. (Find the link at the end of this article.)
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.
This JDBC driver allows applications to use both JDBC and Structured Query Language in Java (SQLJ) access.
com.ibm.db2.jcc.DB2ConnectionPoolDataSource
java com.ibm.db2.jcc.DB2Jcc -versionThe output for the above example is:
IBM DB2 JDBC Universal Driver Architecture 2.2.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>${UNIVERSAL_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.
com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper
Requires a valid authentication alias.
You can use useTransactionRedirect for both driverType 2 and driverType 4 data sources. To configure the property, use either the wsadmin scripting tool or the administrative console page J2EE resource provider or connection factory custom properties collection . Assign the property the value of true.
The DB2 Universal JDBC Driver provider (XA) is an architecture-neutral JDBC provider for distributed and local DB2 access. Whether you use this provider for Java connectivity or Java Native Interface (JNI) based connectivity depends on the version of DB2 you are running. Application Server Version 6.0 minimally requires DB2 8.1 Fix Pack 6. This version of DB2 only supports XA connectivity over the Java Native Interface (JNI) based connectivity (Type 2) driver. In order to use XA connectivity with the Type 4 driver, DB2 8.1 Fix Pack 7 or higher is required.
The DB2 Universal JDBC Driver (XA) supports two phase transactions and the more advanced data source option offered by Application Server (as opposed to the other option, Version 4 data sources). This driver also allows applications to use both JDBC and SQLJ access.
com.ibm.db2.jcc.DB2XADataSource
${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar
${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar
${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cisuz.jar
You must use the right license JAR file to access a specific database backend.
${DB2UNIVERSAL_JDBC_DRIVER_NATIVEPATH}
com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper
Requires a valid authentication alias.
You can use useTransactionRedirect for both driverType 2 and driverType 4 data sources. To configure the property, use either the wsadmin scripting tool or the administrative console page J2EE resource provider or connection factory custom properties collection . Assign the property the value of true.
java com.ibm.db2.jcc.DB2Jcc -versionexample output of the above:
IBM DB2 JDBC Universal Driver Architecture 2.2.xx
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.
COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource
Requires JDBC driver files: db2java.zip (Note: If you run SQLJ in DB2 Version 8, db2jcc.jar is also required.)
com.ibm.websphere.rsadapter.DB2DataStoreHelper
Does not require a valid authentication alias if Application Server is running on the same machine as the database. Otherwise, connectivity through this driver does require an alias.
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.
COM.ibm.db2.jdbc.DB2XADataSource
Requires JDBC driver files: db2java.zip (Note: If you run SQLJ in DB2 Version 8, db2jcc.jar is also required.)
com.ibm.websphere.rsadapter.DB2DataStoreHelper
Does not require a valid authentication alias if Application Server is running on the same machine as the database. Otherwise, connectivity through this driver does require an alias.
For more information on DB2, click the link to the DB2 product Web pages, at the end of this article. The DB2 product pages have links to support documentation and other literature.
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.
com.ibm.db2.jdbc.app.UDBConnectionPoolDataSource
Requires JDBC driver files: db2_classes.jar
com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper
Does not require an authentication alias.
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.
com.ibm.db2.jdbc.app.UDBXADataSource
Requires JDBC driver files: db2_classes.jar
com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper
Does not require an authentication alias.
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.
com.ibm.as400.access.AS400JDBCConnectionPoolDataSource
Requires JDBC driver files: jt400.jar
com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper
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.
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.
com.ibm.as400.access.AS400JDBCXADataSource
Requires JDBC driver files: jt400.jar
com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper
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 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. This provider is intended for remote connections to DB2 running on iSeries. For use with Application Server on Windows, supported UNIX systems, or workstation-based Linux systems, it therefore requires the DB2 Connect Driver (which is available from DB2).
COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource
Requires JDBC driver files: db2java.zip (Note: If you run SQLJ in DB2 Version 8, db2jcc.jar is also required.)
com.ibm.websphere.rsadapter.DB2DataStoreHelper
Does not require a valid authentication alias.
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. This provider is intended for remote connections to DB2 running on iSeries; for use with Application Server on Windows, supported UNIX systems, or workstation-based Linux systems, it therefore requires the DB2 Connect Driver (which is available from DB2).
COM.ibm.db2.jdbc.DB2XADataSource
Requires JDBC driver files: db2java.zip
com.ibm.websphere.rsadapter.DB2DataStoreHelper
Does not require a valid authentication alias.
This JDBC provider is deprecated because it corresponds to a version of the iSeries operating system that WebSphere Application Server Version 6.x does not support. You must now use iSeries V5R2 or a later release of the iSeries operating system, for which the WebSphere Application Server administrative console lists one native iSeries DB2 non-XA provider: DB2 UDB for iSeries (Native).
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.
com.ibm.db2.jdbc.app.DB2StdConnectionPoolDataSource
Requires JDBC driver files: db2_classes.jar
com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper
Does not require an authentication alias.
This JDBC provider is deprecated because it corresponds to a version of the iSeries operating system that WebSphere Application Server Version 6.x does not support. You must now use iSeries V5R2 or a later release of the iSeries operating system, for which the administrative console lists one native iSeries DB2 XA provider: DB2 UDB for iSeries (Native XA).
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.
com.ibm.db2.jdbc.app.DB2StdXADataSource
Requires JDBC driver files: db2_classes.jar
com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper
Does not require an authentication alias.
For more information on DB2 for iSeries, click the link to the DB2 UDB for iSeries information center, at the end of this article.
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 JDBC driver allows applications to use both JDBC and Structured Query Language in Java (SQLJ) access.
com.ibm.db2.jcc.DB2ConnectionPoolDataSource
java com.ibm.db2.jcc.DB2Jcc -versionThe output for the above example is:
IBM DB2 JDBC Universal Driver Architecture 2.2.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.
com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper
Requires a valid authentication alias.
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.
com.ibm.db2.jcc.DB2XADataSource
java com.ibm.db2.jcc.DB2Jcc -versionexample output of the above:
IBM DB2 JDBC Universal Driver Architecture 2.2.xx
You must use the right license jar file to access a specific database backend.
com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper
Requires a valid authentication alias.
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. For use with Application Server on Windows, supported UNIX systems, or workstation-based Linux systems, this provider requires DB2 Connect (which is available from DB2).
COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource
Requires JDBC driver files: db2java.zip (Note: If you run SQLJ in DB2 Version 8, db2jcc.jar is also required.)
com.ibm.websphere.rsadapter.DB2DataStoreHelper
Does not require a valid authentication alias.
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. For use with Application Server on Windows, supported UNIX systems, or workstation-based Linux systems, this provider requires DB2 Connect (which is available from DB2).
COM.ibm.db2.jdbc.DB2XADataSource
Requires JDBC driver files: db2java.zip (Note: If you run SQLJ in DB2 Version 8, db2jcc.jar is also required.)
com.ibm.websphere.rsadapter.DB2DataStoreHelper
Does not require a valid authentication alias.
To learn more, click the link to the DB2 for z/OS product Web pages, at the end of this article. These Web pages have links to support documentation and other information.
The Cloudscape JDBC Provider provides the 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.
com.ibm.db2j.jdbc.DB2jConnectionPoolDataSource
Requires the JDBC driver files in db2jcc.jar
com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper
Does not require a valid authentication alias.
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.
com.ibm.db2j.jdbc.DB2jXADataSource
Requires the JDBC driver files in db2jcc.jar
com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper
Does not require a valid authentication alias.
Cloudscape Network Server using Universal JDBC Driver
This Cloudscape driver takes advantage of the Network Server support that the DB2 Universal JDBC Driver type 4 provides. You cannot use any Version 4.0 data sources with Cloudscape.
com.ibm.db2.jcc.DB2ConnectionPoolDataSource
Requires JDBC driver files:
<classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar</classpath> <classpath>${CLOUDSCAPE_JDBC_DRIVER_PATH}/db2j.jar</classpath> <classpath>${CLOUDSCAPE51_JDBC_DRIVER_PATH}/db2j.jar</classpath> <classpath>${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.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 data source. This is instead of hard coding the path of the db2jcc.jar for DB2 data sources.
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.
Requires a valid authentication alias.
See the Cloudscape setup instructions for more information on configuring the Cloudscape Network Server.
For more information, visit the IBM Cloudscape version 5.1.x publications center. Find a link at the end of this article.
(For WebSphere Application Server v6.02, only Cloudscape
v10.0 applies)
The Derby JDBC driver provides JDBC access to the Cloudscape v10.x database by using the framework that is already embedded in WebSphere Application Server for Cloudscape. However, you cannot use any Version 4.0 data sources with Cloudscape v10.x.
org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource
Requires JDBC driver files: derby.jar; full path name: ${WAS_APP_SERVER_ROOT}/derby/lib/derby.jar
com.ibm.websphere.rsadapter.DerbyDataStoreHelper
Does not require a valid authentication alias.
The Derby JDBC driver (XA) provides JDBC access to the Cloudscape v10.x database by using the framework that is already embedded in WebSphere Application Server for Cloudscape. However, you cannot use any Version 4.0 data sources with Cloudscape v10.x.
org.apache.derby.jdbc.EmbeddedXADataSource
Requires JDBC driver files: derby.jar; full path name: ${WAS_APP_SERVER_ROOT}/derby/lib/derby.jar
com.ibm.websphere.rsadapter.DerbyDataStoreHelper
Does not require a valid authentication alias.
The Derby Network Server using the Universal JDBC Driver takes advantage of the Network Server support that the DB2 Universal JDBC Driver type 4 provides. You cannot use any Version 4.0 data sources with Cloudscape v10.x.
com.ibm.db2.jcc.DB2ConnectionPoolDataSource
Requires JDBC driver files:
<classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar</classpath> <classpath>${CLOUDSCAPE_JDBC_DRIVER_PATH}/otherJars/db2jcc.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 Application Server when you set up your DB2 data source. This is instead of hard coding the path of the db2jcc.jar for DB2 data sources.
com.ibm.websphere.rsadapter.DerbyNetworkServerDataStoreHelper
Requires a valid authentication alias.
See the Configuring Derby Version 10 topic
for more information on configuring the Derby Network Server.
To learn more about the new Cloudscape code base,
visit the Open Source Apache Derby Project Web site or the IBM Cloudscape
version 10.0 information center. See the links at the end of this article.
The Informix JDBC Driver is a Type 4 JDBC driver that provides JDBC access to the Informix database.
com.informix.jdbcx.IfxConnectionPoolDataSource
ifxjdbc.jar ifxjdbcx.jar
com.ibm.websphere.rsadapter.InformixDataStoreHelper
Requires a valid authentication alias.
The Informix JDBC Driver (XA) is a Type 4 JDBC driver that provides XA-compliant JDBC access to the Informix database.
com.informix.jdbcx.IfxXADataSource
ifxjdbc.jar ifxjdbcx.jar
com.ibm.websphere.rsadapter.InformixDataStoreHelper
Requires a valid authentication alias.
For more information on Informix, visit the IBM Informix product family Web pages. Find the link at the end of this article.
The Sybase jConnect JDBC driver is a Type 4 JDBC driver that provides JDBC access to the Sybase database.
com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource
Requires JDBC driver files: jconn2.jar.
com.ibm.websphere.rsadapter.SybaseDataStoreHelper
Requires a valid authentication alias.
The Sybase jConnect JDBC driver (XA) is a Type 4 JDBC driver that provides XA-compliant JDBC access to the Sybase database.
com.sybase.jdbc2.jdbc.SybXADataSource
Requires JDBC driver files: jconn2.jar.
com.ibm.websphere.rsadapter.SybaseDataStoreHelper
Requires a valid authentication alias.
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.pool.OracleConnectionPoolDataSource
Requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)
com.ibm.websphere.rsadapter.OracleDataStoreHelper(Note: If you are running Oracle10g, use com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper.)
Requires a valid authentication alias.
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.xa.client.OracleXADataSource
Requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)
com.ibm.websphere.rsadapter.OracleDataStoreHelper(Note: If you are running Oracle10g, use com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper.)
Requires a valid authentication alias.
DataDirect ConnectJDBC type 4 driver for MS SQL Server is a Type 4 JDBC driver that provides JDBC access to the MS SQL Server 2000 database. This provider is for use only with the Connect JDBC driver purchased from DataDirect Technologies.
com.ddtek.jdbcx.sqlserver.SQLServerDataSource
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.)
com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper
Requires a valid authentication alias.
DataDirect ConnectJDBC type 4 driver for MS SQL Server (XA) is a Type 4 JDBC driver that provides XA-compliant JDBC access to the MS SQL Server 2000 database. This provider is for use only with the Connect JDBC driver purchased from DataDirect Technologies.
com.ddtek.jdbcx.sqlserver.SQLServerDataSource.
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.)
com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper
Requires a valid authentication alias.
WebSphere embedded ConnectJDBC driver for MS SQL Server is a Type 4 JDBC driver that provides JDBC access to the MS SQL Server 2000 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.
com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource.
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.)
All of the JAR files in the previous list are shipped with WebSphere Application Server and are installed automatically with the product. They are also updated automatically when you apply WebSphere Application Server service packs.
com.ibm.websphere.rsadapter.WSConnectJDBCDataStoreHelper
Requires a valid authentication alias.
WebSphere embedded ConnectJDBC driver for MS SQL Server (XA) is a Type 4 JDBC driver that supports two-phase commit transactions on connections with the MS SQL Server 2000 database. This JDBC driver ships with WebSphere Application Server. Use this provider with the IBM WebSphere Connect JDBC driver embedded in WebSphere Application Server. Do not use it with the DataDirect Connect JDBC driver purchased separately from DataDirect Technologies.
com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource.
sqlserver.jar base.jar and util.jar.An additional file, the spy.jar file, is optional. You need spy.jar for spy logging, which is a form of JDBC driver-level trace.
All of the JAR files in the previous list are shipped with WebSphere Application Server and are installed automatically with the product. They are also updated automatically when you apply WebSphere Application Server service packs.
com.ibm.websphere.rsadapter.WSConnectJDBCDataStoreHelper
Requires a valid authentication alias.
Patches to the IBM WebSphere Connect JDBC driver jar files are installed automatically when you apply WebSphere Application Server service packs. However, to update Microsoft SQL Server-side programs for this JDBC driver, you must go to the IBM FTP site for WebSphere Application Server embedded product updates. Find the link at the end of this article.
An important server-side program is Stored Procedures for the Java Transaction API (JTA). Whether you need to run one or two phase transactions with the XA-enabled IBM WebSphere Connect JDBC driver, you must install Stored Procedures for JTA on all machines that run Microsoft SQL. The WebSphere Application Server installation disks contain a base level of Stored Procedures for JTA. Go to the previously listed FTP site for updates to this API.
This type 3 JDBC driver for MS SQL Server is deprecated in WebSphere Application Server Version 6.0. Therefore it is no longer an available choice among provider types in the administrative console.
For best results with WebSphere Application Server JDBC access to MS SQL Server, use only JDBC drivers that are not marked for deprecation. However, if you must continue using a deprecated driver for JDBC access to MS SQL Server, you can configure it through the WebSphere Application Server administrative console. Follow the steps listed in Configuring a JDBC provider using the administrative console . Be sure to select User-defined for the database type. This selection triggers the console to display default class files, data source interfaces, and so on for your user-defined JDBC provider type. Replace those defaults with the following settings that are specific to the DataDirect SequeLink type 3 JDBC driver.
com.ddtek.jdbcx.sequelink.SequeLinkDataSource
sljc.jar and spy-sl.jar(The JDBC driver shipped with WebSphere Application Server requires the sljc.jar and the spy-sl.jar files. The JDBC driver purchased from DataDirect requires the sljc.jar and the spy.jar files. The spy.jar and spy-sl.jar files are optional. You need these files to enable spy logging.)
com.ibm.websphere.rsadapter.SequeLinkDataStoreHelper
Requires a valid authentication alias.
The DataDirect SequeLink type 3 JDBC driver requires installation of SequeLink Server on all machines running MS SQL Server. See the readme.html file found in the DataDirect folder on the WebSphere Application Server CD for instructions on how to install SequeLink Server. (Install SequeLink Server from the WebSphere Application Server CD only if you are using the SequeLink JDBC driver embedded in WebSphere. Otherwise, install a copy of SequeLink Server purchased from DataDirect Technologies.)
Patches to the IBM WebSphere SequeLink JDBC driver jar files are installed automatically when applying WebSphere Application Server service packs. If updates are ever needed for the Microsoft SQL Server-side installables (SequeLink server) for the IBM WebSphere SequeLink JDBC driver, they will be made available from the FTP site for MS SQL Server-side JDBC driver updates. See the FTP link at the end of this article.
This type 4 JDBC driver for MS SQL Server 2000 is deprecated in WebSphere Application Server Version 6.0. Therefore it is no longer an available choice among provider types in the administrative console.
For best results with WebSphere Application Server JDBC access to MS SQL Server, use only JDBC drivers that are not marked for deprecation. However, if you must continue using a deprecated driver for JDBC access to MS SQL Server, you can configure it through the WebSphere Application Server administrative console. Follow the steps listed in Configuring a JDBC provider using the administrative console . Be sure to select User-defined for the database type. This selection triggers the console to display default class files, data source interfaces, and so on for your user-defined JDBC provider type. Replace those defaults with the following settings that are specific to the Microsoft JDBC driver for MS SQL Server 2000.
com.microsoft.jdbcx.sqlserver.SQLServerDataSource
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.)
com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper
Requires a valid authentication alias.