Vendor-specific data sources minimum required settings

 

+

Search Tips   |   Advanced Search

 

Use this table as an at-a-glance reference of JDBC providers that can be defined for use with WAS V6.x, to establish data sources for transacting with relational databases. A list that contains detailed requirements for creating data sources with these providers follows the table. (The list also contains information about JDBC providers that are deprecated in WAS V6.x.)

Database type JDBC Provider Transaction support Other considerations
DB2 on Windows, UNIX, or workstation-based LINUX DB2 Universal JDBC Provider One phase only  
DB2 Universal JDBC Provider (XA) One and two phase

The XA implementation is not supported in WAS run on workstation-based LINUX

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 DB2 UDB for iSeries (Native) One phase only

Recommended for use with WAS run on iSeries

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

Recommended for use with WAS run on iSeries

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

-Only for use with WebSphere Application Server run on z/OS

-Only driver type 4 is supported

-Does not support V4 data sources

DB2 legacy CLI-based Type 2 JDBC Provider One phase only

-Only for use with WebSphere Application Server run on Windows, UNIX, or workstation-based LINUX

- Requires the DB2 Connect driver (available from DB2)

DB2 legacy CLI-based Type 2 JDBC Provider (XA) One and two phase

-Only for use with WAS run on Windows, UNIX, or workstation-based LINUX

- Requires the DB2 Connect driver (available from DB2)

DB2 on z/OS DB2 for z/OS Local JDBC Provider (RRS) One and two phase

Only for use with WAS run on z/OS

DB2 Universal JDBC Provider One phase only  
DB2 Universal JDBC Provider (XA) One and two phase

-Only driver type 4 is supported in WAS run on z/OS

-Does not support V4 data sources in WAS run on z/OS

DB2 legacy CLI-based Type 2 JDBC Provider One phase only

-Only for use with WAS run on Windows, UNIX, or workstation-based LINUX

- Requires the DB2 Connect program (available from DB2)

DB2 legacy CLI-based Type 2 JDBC Provider (XA) One and two phase

-Only for use with WAS run on Windows, UNIX, or workstation-based LINUX

- Requires the DB2 Connect program (available from DB2)

Cloudscape Cloudscape JDBC Provider One phase only

- Not for use in clustering environment: Cloudscape is accessible from a single JVM only

- Does not support Version 4 data sources

Cloudscape JDBC Provider (XA) One and two phase

- Not for use in clustering environment: Cloudscape is accessible from a single JVM only

- Does not support Version 4 data sources

Cloudscape Network Server using Universal JDBC driver One phase only Does not support V4 data sources
Informix Informix JDBC Driver One phase only  
Informix JDBC Driver (XA) One and two phase  
Sybase Sybase JDBC Driver One phase only  
Sybase JDBC Driver (XA) One and two phase  
Oracle Oracle JDBC Driver One phase only  
Oracle JDBC Driver (XA) One and two phase  
MS SQL Server DataDirect ConnectJDBC type 4 driver for MS SQL Server One phase only Only for use with the corresponding driver from DataDirect Technologies
DataDirect ConnectJDBC type 4 driver for MS SQL Server (XA) One and two phase Only for use with the corresponding driver from DataDirect Technologies
WebSphere embedded ConnectJDBC driver for MS SQL Server One phase only

- Not available for Application Server on z/OS

- Cannot be used outside of WAS environment

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

- Not available for Application Server on z/OS

- Cannot be used outside of WAS environment

 

Detailed data source requirements per JDBC provider and platform

The following list contains the requirements for creating data sources with every JDBC provider type that is supported in WAS V6.x. 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 custom properties list. Rather, inclusion in the list means that a value is typically required for that field.

Important: After you determine the type of 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 WAS. Consult the Supported hardware and software Web page

  1. DB2 on Windows, UNIX, or workstation-based LINUX
  2. DB2 UDB for iSeries
  3. DB2 on z/OS, connecting to Application Server on Windows, UNIX, or workstation-based LINUX
  4. Cloudscape
  5. Informix
  6. Sybase
  7. Oracle
  8. MS SQL Server

 

DB2 on Windows, UNIX, or workstation-based LINUX

  1. DB2 Universal JDBC Provider

    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 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.

    The DB2 Universal JDBC Driver Provider supports one phase data source 

    com.ibm.db2.jcc.DB2ConnectionPoolDataSource

    Requires JDBC driver files:

    db2jcc.jar After you install DB2, one can find this jar file in the DB2 java directory. For Type 4 JDBC driver support from a client machine where DB2 is not installed, copy this file to the local machine. If you install any fixes or upgrades to DB2, update this file as well. You must also set the DB2UNIVERSAL_JDBC_DRIVER_PATH path variable to point to the db2jcc.jar file. 

    java com.ibm.db2.jcc.DB2Jcc -version

    The output for the above example is 

    IBM DB2 JDBC Universal Driver Architecture 2.2.xx
    db2jcc_license_cu.jar DB2 Universal JDBC driver license file that allows access to the DB2 Universal database. Use this jar file or the next one to gain access to the database. This jar file ships with WAS in a directory defined by ${UNIVERSAL_JDBC_DRIVER_PATH}environment variable.
    db2jcc_license_cisuz.jar DB2 Universal JDBC driver license file that allows access to the following databases:

    • DB2 Universal
    • DB2 for iSeries
    • DB2 for z/OS
    • SQLDS

    The db2jcc_license_cisuz.jar file 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.

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • databaseName This is an actual database name if the driverType is set to 4, or a locally cataloged database name if the driverType is set to 2.

    • driverType The JDBC connectivity type of a data source. There are two permitted values: 2 and 4. If you want to use Universal JDBC Type 2 driver, set this value to 2. If you want to use Universal JDBC Type 4 driver, set this value to 4.

    • serverName The TCP/IP address or host name for the Distributed Relational Database Architecture (DRDA) server. Provide a value for this property only if your driverType is set to 4. This property is not required if your driverType is set to 2.

    • portNumber The TCP/IP port number where the DRDA server resides. Provide a value for this property only if your driverType is set to 4. This property is not required if your driverType is set to 2.

  2. DB2 Universal JDBC Provider (XA)

    The DB2 Universal JDBC 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 v6 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, V4 data sources). This driver also allows applications to use both JDBC and SQLJ access.

    The DB2 Universal JDBC Driver Provider supports the two phase data source 

    com.ibm.db2.jcc.DB2XADataSource

    Requires JDBC driver files:

    db2jcc.jar DB2 Universal JDBC Driver JAR file. After you install DB2, one can find this JAR file in the DB2 Java directory. For Type 4 JDBC driver support from a client machine where DB2 is not installed, copy this file to the local machine. If you install any fixes or upgrades to DB2, update this file as well. You must also specify the fully qualified path of db2jcc.jar as the value of the DB2UNIVERSAL_JDBC_DRIVER_PATH environment variable 

    ${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar
    db2jcc_License_cu.jar DB2 Universal JDBC driver license file that allows access to the DB2 Universal database. Use this JAR file or the next one to gain access to the database. This JAR file ships with WAS in the WAS_HOME/universalDriver/lib directory.

    Class path 

    ${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_License_cu.jar
    db2jcc_License_cisuz.jar DB2 Universal JDBC driver license file that allows access to the following databases:

    • DB2 Universal
    • DB2 for iSeries
    • DB2 for z/OS
    • SQLDS

    Class path 

    ${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_License_cisuz.jar

    You must use the right license JAR file to access a specific database backend.

  3. The native files required by the DB2 Universal JDBC Driver in WAS. Use the following library path 

    ${DB2UNIVERSAL_JDBC_DRIVER_NATIVEPATH}

    4. Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    databaseName This is an actual database name if the driverType is set to 4, or a locally cataloged database name if the driverType is set to 2.
    driverType The JDBC connectivity type of a data source. There are two permitted values: 2 and 4. If you want to use Universal JDBC Type 2 XA driver, set this value to 2. If you want to use Universal JDBC Type 4 XA driver (which requires DB2 8.1 Fix Pack 7 or higher), set this value to 4.
    serverName The TCP/IP address or host name for the Distributed Relational Database Architecture (DRDA) server. Provide a value for this property only if your driverType is set to 4. This property is not required if your driverType is set to 2.
    portNumber The TCP/IP port number where the DRDA server resides. Provide a value for this property only if your driverType is set to 4. This property is not required if your driverType is set to 2.

    Tip: To find the level of universal driver you are using, issue the following DB2 command 

    java com.ibm.db2.jcc.DB2Jcc -version
    example output of the above 

     IBM DB2 JDBC Universal Driver Architecture 2.2.xx

    DB2 legacy CLI-based Type 2 JDBC Driver

    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

    Requires JDBC driver files: db2java.zip (

    Note: If you run SQLJ in DB2 V8, db2jcc.jar is also required.)

    Requires DataStoreHelper class 

    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.

    Requires properties:

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

    DB2 legacy CLI-based Type 2 JDBC Driver (XA)

    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

    Requires JDBC driver files: db2java.zip (

    Note: If you run SQLJ in DB2 V8, db2jcc.jar is also required.)

    Requires DataStoreHelper class 

    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.

    Requires properties:

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

For more information on DB2, visit the DB2 Web site at: http://www.ibm.com/software/data/db2/.

For information on configuring WAS for DB2 access, see the Configuring DB2 article.

 

DB2 UDB for iSeries

    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 V5R2, or later releases.

    DB2 UDB for iSeries (Native V5R2 and later) supports one phase data source 

    com.ibm.db2.jdbc.app.UDBConnectionPoolDataSource

    Requires JDBC driver files: db2_classes.jar

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper

    Does not require an authentication alias.

    Requires properties:

    • databaseName The name of the relational database to which the data source connections are established. This name must appear in the iSeries Relational Database Directory. The default is *LOCAL.

    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 V5R2 or later releases.

    DB2 UDB for iSeries (Native XA - V5R2 and later) supports two phase data source 

    com.ibm.db2.jdbc.app.UDBXADataSource

    Requires JDBC driver files: db2_classes.jar

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper

    Does not require an authentication alias.

    Requires properties:

    • databaseName The name of the relational database to which the data source connections are established. This name must appear in the iSeries Relational Database Directory. The default is *LOCAL.

    DB2 UDB for iSeries (Toolbox)

    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

    Requires JDBC driver files: jt400.jar

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper

    Does not require an authentication alias if WAS 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.

    Requires properties:

    • serverName The name of the server from which the data source obtains connections. Example: myserver.mydomain.com.

  1. DB2 UDB for iSeries (Toolbox XA)

    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

    Requires JDBC driver files: jt400.jar

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper

    Does not require an authentication alias if WAS 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.

    Requires properties:

    • serverName The name of the server from which the data source obtains connections. Example: myserver.mydomain.com.

  2. DB2 legacy CLI-based Type 2 JDBC Driver

    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, UNIX, or workstation-based LINUX, it therefore requires the DB2 Connect Driver (which is available from DB2).

    DB2 legacy CLI-based Type 2 JDBC Driver supports one phase data source 

    COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource

    Requires JDBC driver files: db2java.zip (

    Note: If you run SQLJ in DB2 V8, db2jcc.jar is also required.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2DataStoreHelper

    Does not require a valid authentication alias.

    Requires properties:

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

  3. DB2 legacy CLI-based Type 2 JDBC Driver (XA)

    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, UNIX, or workstation-based LINUX, it therefore requires the DB2 Connect Driver (which is available from DB2).

    DB2 legacy CLI-based Type 2 JDBC Driver (XA) supports two phase data source 

    COM.ibm.db2.jdbc.DB2XADataSource

    Requires JDBC driver files: db2java.zip (

    Note: If you run SQLJ in DB2 V8, db2jcc.jar is also required.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2DataStoreHelper

    Does not require a valid authentication alias.

    Requires properties:

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

  4. DB2 UDB for iSeries (Native - V5 Release 1 and earlier) -- Deprecated

    This JDBC provider is deprecated because it corresponds to a version of the iSeries operating system that WAS V6.x does not support. You must now use iSeries V5R2 or a later release of the iSeries operating system, for which the WAS 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.

    DB2 UDB for iSeries (Native V5R1 and earlier) supports one phase data source: 

    com.ibm.db2.jdbc.app.DB2StdConnectionPoolDataSource

    Requires JDBC driver files: db2_classes.jar

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper

    Does not require an authentication alias.

    Requires properties:

    • databaseName The name of the relational database to which the data source connections are established. This name must appear in the iSeries Relational Database Directory. The default is *LOCAL.

  5. DB2 UDB for iSeries (Native XA - V5 Release 1 and earlier) -- Deprecated

    This JDBC provider is deprecated because it corresponds to a version of the iSeries operating system that WAS V6.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.

    DB2 UDB for iSeries (Native XA - V5R1 and earlier) supports two phase data source 

    com.ibm.db2.jdbc.app.DB2StdXADataSource

    Requires JDBC driver files: db2_classes.jar

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper

    Does not require an authentication alias.

    Requires properties:

    • databaseName The name of the relational database to which the data source connections are established. This name must appear in the iSeries Relational Database Directory. The default is *LOCAL.

For more information on DB2 UDB for iSeries, visit the DB2 Web site at: http://www.ibm.com/software/data/db2/

 

DB2 on z/OS, connecting to Application Server on Windows, UNIX, or workstation-based LINUX

  1. DB2 Universal JDBC Provider

    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 WAS Version 5.0.2, the product now supports both Type 2 and Type 4 JDBC drivers. To use the Type 4 driver, install DB2 V8.1 or a later version. To use the Type 2 driver, install DB2 V8.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.

    The DB2 Universal JDBC Driver Provider supports one phase data source 

    com.ibm.db2.jcc.DB2ConnectionPoolDataSource
    Requires JDBC driver files:

    db2jcc.jar After you install DB2, one can find this jar file in the DB2 java directory. For Type 4 JDBC driver support from a client machine where DB2 is not installed, copy this file to the local machine. If you install any fixes or upgrades to DB2, update this file as well. You must also set the DB2UNIVERSAL_JDBC_DRIVER_PATH path variable to point to the db2jcc.jar file. 

    java com.ibm.db2.jcc.DB2Jcc -version
    The output for the above example is 

    IBM DB2 JDBC Universal Driver Architecture 2.2.xx
    db2jcc_license_cu.jar DB2 Universal JDBC driver license file that allows access to the DB2 Universal database. Use this jar file or the next one to gain access to the database. This jar file ships with WAS in a directory defined by ${UNIVERSAL_JDBC_DRIVER_PATH}environment variable.
    db2jcc_license_cisuz.jar DB2 Universal JDBC driver license file that allows access to the following databases:

    • DB2 Universal
    • DB2 for iSeries
    • DB2 for z/OS
    • SQLDS

    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.

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • databaseName This is an actual database name if the driverType is set to 4, or a locally cataloged database name if the driverType is set to 2.

    • driverType The JDBC connectivity type of a data source. There are two permitted values: 2 and 4. If you want to use Universal JDBC Type 2 driver, set this value to 2. If you want to use Universal JDBC Type 4 driver, set this value to 4.

    • serverName The TCP/IP address or host name for the Distributed Relational Database Architecture (DRDA) server. Provide a value for this property only if your driverType is set to 4. This property is not required if your driverType is set to 2.

    • portNumber The TCP/IP port number where the DRDA server resides. Provide a value for this property only if your driverType is set to 4. This property is not required if your driverType is set to 2.

  2. DB2 Universal JDBC Provider (XA)

    The DB2 Universal JDBC Driver (XA) is an architecture-neutral JDBC driver for distributed and local DB2 access. In WAS V5.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, install DB2 V8.1 Fix Pack 2 or a later version. This driver supports two phase transactions and the WAS V5.0 data source. This driver allows applications to use both JDBC and SQLJ access.

    The DB2 Universal JDBC Driver Provider supports the two phase data source 

    com.ibm.db2.jcc.DB2XADataSource

    Requires JDBC driver files:

    • db2jcc.jar After you install DB2, one can find this .jar file in the DB2 java directory. For Type 4 JDBC driver support from a client machine where DB2 is not installed, copy this file to the local machine. If you install any fixes or upgrades to DB2, update this file as well. You must also set the DB2UNIVERSAL_JDBC_DRIVER_PATH environment variable to point to the db2jcc.jar file. See the Cloudscape section for more information on the DB2UNIVERSAL_JDBC_DRIVER_PATH environment variable.

      Note: To find the level of universal driver you are using, issue the following DB2 command 

      java com.ibm.db2.jcc.DB2Jcc -version
      example output of the above 

       IBM DB2 JDBC Universal Driver Architecture 2.2.xx

    • db2jcc_license_cu.jar This is the DB2 Universal JDBC driver license file that allows access to the DB2 Universal database. Use this jar file or the next one to gain access to the database. This jar file ships with WAS in the WAS_HOME/universalDriver/lib directory.

    • db2jcc_license_cisuz.jar This is the DB2 Universal JDBC driver license file that allows access to the following databases:

      • DB2 Universal

      • DB2 for iSeries

      • DB2 for z/OS

      • SQLDS

      You must use the right license jar file to access a specific database backend.

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • databaseName This is a locally cataloged database name.

    • driverType This is the JDBC connectivity type of a data source. If you are running a version of DB2 prior to DB2 V8.1 FP6, you are restricted to using only the type 2 driver.

    • serverName The TCP/IP address or host name for the Distributed Relational Database Architecture (DRDA) server. Provide a value for this property only if your driverType is set to 4. This property is not required if your driverType is set to 2.

    • portNumber The TCP/IP port number where the DRDA server resides. Provide a value for this property only if your driverType is set to 4. This property is not required if your driverType is set to 2.

  3. DB2 legacy CLI-based Type 2 JDBC Driver

    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, UNIX, or workstation-based LINUX, this provider requires DB2 Connect (which is available from DB2).

    DB2 legacy CLI-based Type 2 JDBC Driver supports one phase data source 

    COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource

    Requires JDBC driver files: db2java.zip (

    Note: If you run SQLJ in DB2 V8, db2jcc.jar is also required.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2DataStoreHelper

    Does not require a valid authentication alias.

    Requires properties:

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

  4. DB2 legacy CLI-based Type 2 JDBC Driver (XA)

    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, UNIX, or workstation-based LINUX, this provider requires DB2 Connect (which is available from DB2).

    DB2 legacy CLI-based Type 2 JDBC Driver (XA) supports two phase data source 

    COM.ibm.db2.jdbc.DB2XADataSource

    Requires JDBC driver files: db2java.zip (

    Note: If you run SQLJ in DB2 V8, db2jcc.jar is also required.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2DataStoreHelper

    Does not require a valid authentication alias.

    Requires properties:

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

For more information on DB2 for z/OS, visit the DB2 Web site at: http://www.ibm.com/software/data/db2/.

 

Cloudscape

  1. Cloudscape JDBC Provider

    The Cloudscape JDBC Provider provides the JDBC access to the Cloudscape database. This Cloudscape JDBC driver used the embedded framework. We cannot use any V4.0 data sources with Cloudscape.

    Cloudscape JDBC Provider supports one phase data source 

    
com.ibm.db2j.jdbc.DB2jConnectionPoolDataSource

    Requires JDBC driver files: db2j.jar.

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper

    Does not require a valid authentication alias.

    Requires properties:

    • databaseName The name of the database from which the data source obtains connections. If you do not specify a fully qualified path name, Application Server uses the default location of WAS_HOME./cloudscape (or the equivalent default for a UNIX or LINUX environment).

      • Example database path name for Windows: c:\temp\sampleDB

      • Example database path name for UNIX or LINUX: /tmp/sampleDB

      If no database currently exists for the path name you want to specify, simply append ;create=true to the path name to create a database dynamically. (For example: c:\temp\sampleDB;create=true)

    Cloudscape JDBC Provider (XA)

    The Cloudscape JDBC Provider (XA) provides the XA-compliant JDBC access to the Cloudscape database. This Cloudscape JDBC driver uses the embedded framework. We cannot use any V4.0 data sources with Cloudscape.

    Cloudscape JDBC Provider (XA) supports two phase data source 

    
com.ibm.db2j.jdbc.DB2jXADataSource

    Requires JDBC driver files: db2j.jar

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper

    Does not require a valid authentication alias.

    Requires properties:

    • databaseName The name of the database from which the data source obtains connections. If you do not specify a fully qualified path name, Application Server uses the default location of WAS_HOME./cloudscape (or the equivalent default for a UNIX or LINUX environment).

      • Example database path name for Windows: c:\temp\sampleDB

      • Example database path name for UNIX or LINUX: /tmp/sampleDB

      If no database currently exists for the path name you want to specify, simply append ;create=true to the path name to create a database dynamically. (For example: c:\temp\sampleDB;create=true)

    Cloudscape Network Server using Universal JDBC driver

    This Cloudscape driver takes advantage of the Network Server support that the DB2 universal Type 4 JDBC driver provides. We cannot use any V4.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

    Requires JDBC driver files:

    • db2jcc.jar If you install and run DB2, use the db2jcc.jar file that comes with DB2. To do that, the classpath in the JDBC template for Cloudscape network server is set to be 

      <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 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.

    • db2jcc_license_cu.jar This file is the DB2 Universal JDBC license file that provides access to the Cloudscape databases using the Network Server framework. Use this file to gain access to the database. This file ships with WebSphere and is located in ${UNIVERSAL_JDBC_DRIVER_PATH}.

      Note: UNIVERSAL_JDBC_DRIVER_PATH is 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 versions of the db2jcc.jar file.

      Note: DB2UNIVERSAL_JDBC_DRIVER_PATH is a WebSphere environment variable that 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.

      Note: Cloudscape requires only db2jcc_license_c.jar; however, WAS uses db2jcc_license_cu.jar because this works for both DB2 UDB and Cloudscape.

    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.

    Requires a valid authentication alias.

    Requires properties:

    • databaseName The name of the database from which the data source obtains connections. If you do not specify a fully qualified path name, Application Server uses the default location of WAS_HOME./cloudscape (or the equivalent default for a UNIX or LINUX environment).

      • Example database path name for Windows: c:\temp\sampleDB

      • Example database path name for UNIX or LINUX: /tmp/sampleDB

      If no database currently exists for the path name you want to specify, simply append ;create=true to the path name to create a database dynamically. (For example: c:\temp\sampleDB;create=true)

    • driverType Only the Type 4 driver is allowed.

    • serverName The TCP/IP address or the host name for the Distributed Relational Database Architecture (DRDA) server.

    • portNumber The TCP/IP port number where the DRDA server resides. The default value is port 1527.

    • retrieveMessagesfromServerOnGetMessage This property is required by WAS, not the database. The default value is false. You must set the value of this property to true, to enable text retrieval using the SQLException.getMessage() method.

    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

    Informix JDBC Driver

    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

    Requires JDBC driver files 

       ifxjdbc.jar
   ifxjdbcx.jar

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.InformixDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • serverName The name of the Informix instance on the server. Example: ol_myserver.

    • portNumber The port on which the instances listen. Example: 1526.

    • ifxIFXHOST Either the IP address or the host name of the machine that is running the Informix database to which you want to connect. Example: myserver.mydomain.com.

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

    • informixLockModeWait Although not required, this property enables you to set the number of seconds that Informix software waits for a lock. By default, Informix code throws an exception if it cannot immediately acquire a lock. Example: 2.

    Informix JDBC Driver (XA)

    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

    Requires JDBC driver files 

       ifxjdbc.jar
   ifxjdbcx.jar

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.InformixDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • serverName The name of the Informix instance on the server. Example: ol_myserver.

    • portNumber The port on which the instances listen. Example: 1526.

    • ifxIFXHOST Either the IP address or the host name of the machine that is running the Informix database to which you want to connect. Example: myserver.mydomain.com.

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

    • informixLockModeWait Although not required, this property enables you to set the number of seconds that Informix software waits for a lock. By default, Informix code throws an exception if it cannot immediately acquire a lock. Example: 2.

For more information on Informix, visit the Informix Web site at: http://www.ibm.com/software/data/informix/

 

Sybase

    Sybase JDBC Driver

    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

    Requires JDBC driver files: jconn2.jar.

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.SybaseDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • serverName The name of the database server. Example: myserver.mydomain.com.

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

    • portNumber The TCP/IP port number through which all communications to the server take place. Example: 4100.

    • connectionProperties A custom property required for applications containing EJB 2.0 enterprise beans. Value: SELECT_OPENS_CURSOR=true(Type: java.lang.String)

    Sybase JDBC Driver (XA)

    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

    Requires JDBC driver files: jconn2.jar.

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.SybaseDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • serverName The name of the database server. Example: myserver.mydomain.com

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

    • portNumber The TCP/IP port number through which all communications to the server take place. Example: 4100.

    • connectionProperties A custom property required for applications containing EJB 2.0 enterprise beans. Value: SELECT_OPENS_CURSOR=true(Type: java.lang.String)

For more information on Sybase, visit the Sybase Web site at: http://www.sybase.com/

 

Oracle

    Oracle JDBC Driver

    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

    Requires JDBC driver files: ojdbc14.jar. (

    Note: If you require Oracle trace, use ojdbc14_g.jar.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.OracleDataStoreHelper
    (

    Note: If you are running Oracle10g, use com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper.

    Requires a valid authentication alias.

    Requires properties:

    • URL The URL that indicates the database from which the data source obtains connections. Example: jdbc:oracle:thin:@myServer:1521:myDatabase, where myServer is the server name, 1521 is the port it is using for communication, and myDatabase is the database name.

    Oracle JDBC Driver (XA)

    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

    Requires JDBC driver files: ojdbc14.jar. (

    Note: If you require Oracle trace, use ojdbc14_g.jar.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.OracleDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • URL The URL that indicates the database from which the data source obtains connections. Example: jdbc:oracle:thin:@myServer:1521:myDatabase, where myServer is the server name, 1521 is the port it is using for communication, and myDatabase is the database name.

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

    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 Connect JDBC driver purchased from DataDirect Technologies.

    This JDBC provider supports this data source 

     com.ddtek.jdbcx.sqlserver.SQLServerDataSource

    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.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • serverName The name of the server in which MS SQL Server resides. Example: myserver.mydomain.com

    • portNumber The TCP/IP port that MS SQL Server uses for communication. Port 1433 is the default.

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

    DataDirect ConnectJDBC type 4 driver for MS SQL Server (XA)

    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 Connect JDBC driver purchased from DataDirect Technologies.

    This JDBC provider supports this data source 

    com.ddtek.jdbcx.sqlserver.SQLServerDataSource.

    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.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • serverName The name of the server in which MS SQL Server resides. Example: myserver.mydomain.com

    • portNumber The TCP/IP port that MS SQL Server uses for communication. Port 1433 is the default.

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

    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

    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 WAS. 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.

    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 WAS. All the files are located in the WAS_HOME/lib/ directory.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.WSConnectJDBCDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • serverName The name of the server in which MS SQL Server resides. Example: myserver.mydomain.com

    • portNumber The TCP/IP port that MS SQL Server uses for communication. Port 1433 is the default.

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

    WebSphere embedded ConnectJDBC driver for MS SQL Server (XA)

    WebSphere embedded ConnectJDBC 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 JDBC driver ships with WAS. 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.

    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 WAS. All the files are located in the WAS_HOME/lib/ directory.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.WSConnectJDBCDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • serverName The name of the server in which MS SQL Server resides. Example: myserver.mydomain.com

    • portNumber The TCP/IP port that MS SQL Server uses for communication. Port 1433 is the default.

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

    Whether we need to support one or two phase transactions with the WebSphere embedded Connect JDBC XA driver, install Stored Procedures for the Java Transaction API (JTA) on your machine that runs Microsoft SQL. The WAS installation disks provide a base level of Stored Procedures for JTA. (We can find the most current version of the software on the WAS-embedded DataDirect Technologies product update Web page.) Install Stored Procedures for JTA by performing the following steps:

    1. Determine whether you are running the 32-bit or 64-bit MS SQL Server and select the appropriate sqljbc.dll and instjdbc.sql files.

    2. Stop your MS SQL Server service.

    3. Copy the sqljdbc.dll file into your %SQL_SERVER_INSTALL%\Binn\ directory.

    4. Restart the MS SQL Server service.

    5. Run the instjdbc.sql script. (The script can be run by the MS SQL Server Query Analyzer or the ISQL utility).

    We can download the latest patches and upgrades to the WebSphere embedded Connect JDBC driver 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 -- Deprecated

    Because this JDBC provider is deprecated in WebSphere Application Server v6, it is no longer an available option in the administrative console. In its place, use one of the Connect JDBC providers, which are described previously in this section.

    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 provider supports this data source 

     com.ddtek.jdbcx.sequelink.SequeLinkDataSource

    Requires JDBC driver files 

     sljc.jar and
 spy-sl.jar
    (The JDBC driver shipped with WAS 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.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.SequeLinkDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • serverName The name of the server in which SequeLink Server resides. Example: myserver.mydomain.com

    • portNumber The TCP/IP port that SequeLink Server uses for communication. By default, SequeLink Server uses port 19996.

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

    DataDirect SequeLink type 3 JDBC driver for MS SQL Server (XA) -- Deprecated

    Because this JDBC provider is deprecated in WAS v6, it is no longer an available option in the administrative console. In its place, use one of the Connect JDBC providers, which are described previously in this section.

    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 provider supports this data source 

    com.ddtek.jdbcx.sequelink.SequeLinkDataSource

    Requires JDBC driver files 

     sljc.jar and
spy-sl.jar
    (The JDBC driver shipped with WAS 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.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.SequeLinkDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • serverName The name of the server in which SequeLink Server resides. Example: myserver.mydomain.com

    • portNumber The TCP/IP port that SequeLink Server uses for communication. By default, SequeLink Server uses port 19996.

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

    Both of the WebSphere-embedded SequeLink JDBC drivers require 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. (Only install SequeLink Server from the WAS CD if you are using the SequeLink JDBC driver embedded in WebSphere. Otherwise, install a copy of SequeLink Server purchased from DataDirect Technologies.)

    From the following FTP site, one can download the latest patches and upgrades for the version of SequeLink Server that is used with the WebSphere-embedded SequeLink JDBC driver 

    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 -- Deprecated

    Because this JDBC provider is deprecated in WAS v6, it is no longer an available option in the administrative console. In its place, use one of the Connect JDBC providers, which are described previously in this section.

    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

    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.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • serverName The name of the server in which MS SQL Server resides. Example: myserver.mydomain.com

    • portNumber The TCP/IP port that MS SQL Server uses for communication. Port 1433 is the default.

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

    Microsoft JDBC driver for MSSQLServer 2000 (XA) -- Deprecated

    Because this JDBC provider is deprecated in WebSphere Application Server v6, it is no longer an available option in the administrative console. In its place, use one of the Connect JDBC providers, which are described previously in this section.

    Microsoft JDBC driver for MSSQLServer 2000 (XA) is a type 4 JDBC driver that provides XA-compliant JDBC access to the MS SQL Server database.

    This JDBC provider supports this data source 

    com.microsoft.jdbcx.sqlserver.SQLServerDataSource

    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.)

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

    • serverName The name of the server in which MS SQL Server resides. Example: myserver.mydomain.com

    • portNumber The TCP/IP port that MS SQL Server uses for communication. Port 1433 is the default.

    • databaseName The name of the database from which the data source obtains connections. Example: Sample.

For more information on the Microsoft JDBC driver, visit the Microsoft Web site at 

http://www.microsoft.com/sql

 

See Also


Data sources
Resource adapter
JDBC providers

 

Related Tasks


Create a JDBC provider and data source
Create a JDBC provider using the administrative console
Create a data source using the administrative console
Create a JDBC provider and data source using the Java Management Extensions API