WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Data source minimum required settings, by vendor

These properties vary according to the database vendor requirements for JDBC driver implementations. 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
  • Only for use with WebSphere Application Server run on Windows, supported UNIX systems, or supported Linux systems
  • 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 WebSphere Application Server run on Windows, supported UNIX systems, or supported Linux systems
  • Requires the DB2 Connect driver (available from DB2)
DB2 on z/OS
JDBC provider Transaction support Version and other considerations
DB2 Universal JDBC Provider
  • One phase only when connecting to WebSphere Application Server run on Windows, supported UNIX systems, or supported Linux systems
  • One and two phase when connecting to WebSphere Application Server for the z/OS platform, using driver type 2
WebSphere Application Server for the z/OS platform only: For two-phase transaction support, use driver type 2. Application Server then uses RRS to coordinate transaction processing.
DB2 Universal JDBC Provider (XA) One and two phase
  • In WebSphere Application Server run on z/OS, you cannot use driver type 2 with the XA provider; in this case, use only driver type 4.
  • Does not support Version 4 data sources in WebSphere Application Server run on z/OS
DB2 legacy CLI-based Type 2 JDBC Provider One phase only
  • Only for use with WebSphere Application Server run on Windows, supported UNIX systems, or supported Linux systems
  • 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 WebSphere Application Server run on Windows, supported UNIX systems, or supported Linux systems
  • Requires the DB2 Connect program (available from DB2)
Cloudscape Version 5.1.60.x
JDBC provider Transaction support Version and other considerations
Cloudscape JDBC Provider One phase only
  • Not for use in clustered environment: 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 clustered environment: accessible from a single JVM only
  • Does not support Version 4 data sources
Cloudscape Network Server Provider using the Universal JDBC driver One phase only
  • Can be used in clustered environment: a database instance can be accessed by multiple JVMs
  • Does not support XA
  • Does not support Version 4 data sources
[Version 6.0.2]
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
  • Not for use in clustered environment: accessible from a single JVM only
  • Does not support Version 4 data sources

Derby JDBC Provider (XA)

One and two phase
  • Not for use in clustered environment: accessible from a single JVM only
  • Does not support Version 4 data sources

Derby Network Server Provider using the Universal JDBC driver

One phase only
  • Can be used in clustered environment: a database instance can be accessed by multiple JVMs
  • Does not support XA
  • Does not support Version 4 data sources
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
  • Only for use with the corresponding driver from DataDirect Technologies
DataDirect ConnectJDBC Provider, type 4 driver, for MS SQL Server (XA) One and two phase
  • Only for use with the corresponding driver from DataDirect Technologies
IBM WebSphere embedded ConnectJDBC Provider for MS SQL Server One phase only
  • Cannot be used outside of WebSphere Application Server environment
IBM WebSphere embedded ConnectJDBC Provider for MS SQL Server (XA) One and two phase
  • Cannot be used outside of WebSphere Application Server environment

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

Use the following links to navigate the Requirements list. (Each link corresponds to a specific database vendor product and platform.)

DB2 on Windows, supported UNIX systems, or workstation-based Linux systems

[HP-UX] Important: The SafepointPolling technology in the HP Java virtual machine (JVM) for HP-UX might interfere with DB2 transactions. Developed to ensure safepoints for Java threads, SafepointPolling technology generates a signal that can interfere with the signal between WebSphere Application Server and a DB2 database. Database deadlocks often result. Prevent the interference by starting the JVM with the -XX:-SafepointPolling option, which disables SafepointPolling during runtime.
  1. DB2 Universal JDBC Driver 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.

    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
    The provider requires JDBC driver files:
    • db2jcc.jar After you install DB2, you 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, you must update this file as well. You must also set the DB2UNIVERSAL_JDBC_DRIVER_PATH path variable to point to the db2jcc.jar file.
      Note: To find out the version of the DB2 Universal JDBC Driver you are using, issue this DB2 command:
      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 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 WebSphere Application Server in a directory defined by ${UNIVERSAL_JDBC_DRIVER_PATH}environment variable.
    • 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

      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.
    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 Driver type 2 , set this value to 2. If you want to use Universal JDBC Driver type 4, 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.
    • useTransactionRedirect Configure this property as a data source custom property if your backend uses the Database Partitioning Feature (DPF) of DB2 UDB Version 8.2, fix pack 10, and your partitioning key remains constant throughout a transaction. Activating the property affects how the DB2 Universal JDBC Driver directs each connection request that begins a transaction with DB2. The JDBC driver is triggered to send those connection requests to the DPF node that contains the target data of the first directable statement in the transaction, if such a statement exists. DB2 then directs the SQL statement to different partitions as needed; the transaction proceeds normally from the viewpoint of WebSphere Application Server.

      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.

  2. DB2 Universal JDBC Driver provider (XA)

    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.

    The DB2 Universal JDBC Driver provider supports the two phase data source:
    com.ibm.db2.jcc.DB2XADataSource
    
    Requires JDBC driver files:
    • db2jcc.jar This is the DB2 Universal JDBC Driver JAR file. After you install DB2, you 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, you must 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 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 WebSphere Application Server in the WAS_HOME/universalDriver/lib directory. Class path:
      ${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar
    • 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
      Class path:
      ${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cisuz.jar

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

    • The native files required by the DB2 Universal JDBC Driver in WebSphere Application Server. Use the following library path:
      ${DB2UNIVERSAL_JDBC_DRIVER_NATIVEPATH}
    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 Driver type 2 XA, set this value to 2. If you want to use Universal JDBC Driver type 4 XA (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.
    • useTransactionRedirect Configure this property as a data source custom property if your backend uses the Database Partitioning Feature (DPF) of DB2 UDB Version 8.2, fix pack 10, and your partitioning key remains constant throughout a transaction. Activating the property affects how the DB2 Universal JDBC Driver directs each connection request that begins a transaction with DB2. The JDBC driver is triggered to send those connection requests to the DPF node that contains the target data of the first directable statement in the transaction, if such a statement exists. DB2 then directs the SQL statement to different partitions as needed; the transaction proceeds normally from the viewpoint of WebSphere Application Server.

      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.

    Tip: To find the level of DB2 Universal JDBC 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
  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.

    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 Version 8, 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.
  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.

    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 Version 8, 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, 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.

DB2 UDB for iSeries

  1. 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.
  2. 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.
  3. 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 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.

    Requires properties:
    • serverName The name of the server from which the data source obtains connections. Example: myserver.mydomain.com.
  4. 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 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.

    Requires properties:
    • serverName The name of the server from which the data source obtains connections. Example: myserver.mydomain.com.
  5. DB2 legacy CLI-based Type 2 JDBC Driver (Only for use with Application Server on Windows, supported UNIX systems, or workstation-based Linux systems)

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

    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 Version 8, 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.
  6. DB2 legacy CLI-based Type 2 JDBC Driver (XA) (Only for use with Application Server on Windows, supported UNIX systems, or workstation-based Linux systems)

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

    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

    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.
  7. DB2 UDB for iSeries (Native - Version 5 Release 1 and earlier) -- Deprecated

    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.

    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.
  8. DB2 UDB for iSeries (Native XA - Version 5 Release 1 and earlier) -- Deprecated

    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.

    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 for iSeries, click the link to the DB2 UDB for iSeries information center, at the end of this article.

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

  1. DB2 Universal JDBC Driver 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 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.

    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, you 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, you must update this file as well. You must also set the DB2UNIVERSAL_JDBC_DRIVER_PATH path variable to point to the db2jcc.jar file.
      Note: To find out the version of the DB2 Universal JDBC Driver you are using, issue this DB2 command:
      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 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 WebSphere Application Server in a directory defined by ${UNIVERSAL_JDBC_DRIVER_PATH}environment variable.
    • 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

      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 DB2 Universal JDBC Driver type 2 , set this value to 2. If you want to use DB2 Universal JDBC Driver type 4 , 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 Driver provider (XA)

    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 provider supports the two phase data source:
    com.ibm.db2.jcc.DB2XADataSource
    
    Requires JDBC driver files:
    • db2jcc.jar After you install DB2, you 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, you must update this file as well. You must also set the DB2UNIVERSAL_JDBC_DRIVER_PATH environment variable to point to the db2jcc.jar file.
      Note: To find the level of DB2 Universal JDBC 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 WebSphere Application Server 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, supported UNIX systems, or workstation-based Linux systems, 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 Version 8, 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, supported UNIX systems, or workstation-based Linux systems, 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 Version 8, 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.

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.

Cloudscape v5.1.6x

  1. Cloudscape JDBC Provider

    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.

    Cloudscape JDBC Provider supports one phase data source:
    com.ibm.db2j.jdbc.DB2jConnectionPoolDataSource 

    Requires the JDBC driver files in db2jcc.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 supported UNIX system or Linux system environment).
      • Example database path name for Windows: c:\temp\sampleDB
      • Example database path name for supported UNIX systems or Linux systems: /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)
  2. 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. 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 

    Requires the JDBC driver files in db2jcc.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 supported UNIX system or Linux system environment).
      • Example database path name for Windows: c:\temp\sampleDB
      • Example database path name for supported UNIX systems or Linux systems: /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)
  3. 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.

    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, you must 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 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.
    • db2jcc_license_cu.jar This file is the DB2 Universal JDBC Driver 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 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.
      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.
    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 supported UNIX system or Linux system environment).
      • Example database path name for Windows: c:\temp\sampleDB
      • Example database path name for supported UNIX systems or Linux systems: /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 WebSphere Application Server, 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, visit the IBM Cloudscape version 5.1.x publications center. Find a link at the end of this article.

Cloudscape v10.x [Version 6.0.2]

[Version 6.0.2] (For WebSphere Application Server v6.02, only Cloudscape v10.0 applies)

  1. Derby JDBC Provider

    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.

    The Derby JDBC Provider supports one phase data source:
    org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource 

    Requires JDBC driver files: derby.jar; full path name: ${WAS_APP_SERVER_ROOT}/derby/lib/derby.jar

    Requires DataStoreHelper class:
    com.ibm.websphere.rsadapter.DerbyDataStoreHelper

    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/derby (or the equivalent default for a supported UNIX system or Linux system environment).
      • Example database path name for Windows: c:\temp\sampleDB
      • Example database path name for supported UNIX systems or Linux systems: /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)
  2. Derby JDBC Provider (XA)

    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.

    The Derby JDBC Provider (XA) supports two phase data source:
    org.apache.derby.jdbc.EmbeddedXADataSource 

    Requires JDBC driver files: derby.jar; full path name: ${WAS_APP_SERVER_ROOT}/derby/lib/derby.jar

    Requires DataStoreHelper class:
    com.ibm.websphere.rsadapter.DerbyDataStoreHelper

    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/derby (or the equivalent default for a supported UNIX system or Linux system environment).
      • Example database path name for Windows: c:\temp\sampleDB
      • Example database path name for supported UNIX systems or Linux systems: /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)
  3. Derby Network Server using Universal JDBC Driver

    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.

    Use the following one phase data source for the Derby Network Server using the Universal JDBC Driver:
     com.ibm.db2.jcc.DB2ConnectionPoolDataSource

    Requires JDBC driver files:

    • db2jcc.jar If you install and run DB2, you must use the db2jcc.jar file that comes with DB2. To do that, the classpath in the JDBC template for Derby Network Server is set to be:
      <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.
    • db2jcc_license_cu.jar This file is the DB2 Universal JDBC Driver license file that provides access to the Derby 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 mapped to the location in Websphere Application Server where the license jar file 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 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.
      Note: Derby requires only db2jcc_license_c.jar; however, WebSphere Application Server uses db2jcc_license_cu.jar because this works for both DB2 UDB and Derby.
    Requires DataStoreHelper class:
    com.ibm.websphere.rsadapter.DerbyNetworkServerDataStoreHelper

    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/derby (or the equivalent default for a supported UNIX system or Linux system environment).
      • Example database path name for Windows: c:\temp\sampleDB
      • Example database path name for supported UNIX systems or Linux systems: /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 WebSphere Application Server, 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.

    [Version 6.0.2] See the Configuring Derby Version 10 topic for more information on configuring the Derby Network Server.

[Version 6.0.2] 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.

Informix

  1. 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.
      To support IPv6: On AIX and Solaris, IBM Informix Dynamic Server 10.00 with fix pack 1 supports the IPv6 standard. To enable IPv6 on your WebSphere Application Server connection with one of these Informix releases, input your full IPv6 host name for the ifxIFXHOST property.
    • 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.
  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
    
    To use SQLJ: This provider also requires driver file ifxsqlj.jar if you plan to use SQLJ for queries.
    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.
      To support IPv6: On AIX and Solaris, IBM Informix Dynamic Server 10.00 with fix pack 1 supports the IPv6 standard. To enable IPv6 on your WebSphere Application Server connection with one of these Informix releases, input your full IPv6 host name for the ifxIFXHOST property.
    • databaseName The name of the database from which the data source obtains connections. Example: Sample.
    • ifxIFX_XASPEC Turn on this property when multiple users access the same database. Activating the property enforces tight coupling of XA transactions within the same global transaction ID, and requires the transactions to share lock space. These parameters help prevent transaction management errors from occurring in cases of multiple client requests. Turn on the ifxIFX_XASPEC property by assigning it the value of Y or y; either character works because the setting is not case-specific. Turn the property off by assigning it the value of N or n. WebSphere Application Server ignores all other values. Your setting for the property overrides the Informix database system setting.
    • 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 IBM Informix product family Web pages. Find the link at the end of this article.

Sybase

  1. Sybase jConnect for JDBC driver

    The Sybase jConnect JDBC driver is a Type 4 JDBC driver that provides JDBC access to the Sybase database.

    Sybase jConnect JDBC driver supports one phase data source:
    com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource 
    

    Requires JDBC driver files: jconn2.jar.

    [Version 6.0.1] [Version 6.0.2] For IPv6 support: For applications that access Sybase in an IPv6 environment, you must use the Sybase jConnect JDBC driver version 6.0 EBF 12884. This implementation uses different classes and therefore requires a different JAR file and a different implementation class designation. You can define the jConnect JDBC driver v6.0 EBF 12884 in the administrative console by selecting User-defined as the database type on the New JDBC provider page. On the JDBC provider general configuration page, replace the default JAR file name with jconn3.jar. For the implementation class, input com.sybase.jdbc3.jdbc.SybConnectionPoolDataSource. The data store helper class and required properties are the same for all Sybase JDBC drivers.
    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)
  2. Sybase jConnect for JDBC driver (XA)

    The Sybase jConnect JDBC driver (XA) is a Type 4 JDBC driver that provides XA-compliant JDBC access to the Sybase database.

    Sybase jConnect JDBC driver (XA) supports two phase data source:
    com.sybase.jdbc2.jdbc.SybXADataSource 

    Requires JDBC driver files: jconn2.jar.

    [Version 6.0.1] [Version 6.0.2] For IPv6 support: For applications that access Sybase in an IPv6 environment, you must use the Sybase jConnect JDBC driver version 6.0 EBF 12884. This implementation uses different classes and therefore requires a different JAR file and a different implementation class designation. You can define the jConnect JDBC driver v6.0 EBF 12884 in the administrative console by selecting User-defined as the database type on the New JDBC provider page. On the JDBC provider general configuration page, replace the default JAR file name with jconn3.jar. For the implementation class, input com.sybase.jdbc3.jdbc.SybXADataSource. The data store helper class and required properties are the same for all Sybase JDBC drivers.
    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)

Oracle

  1. 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.
  2. 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
    (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.

MS SQL Server

  1. 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 2000 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.
  2. 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 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.

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

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

    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.
  4. IBM WebSphere embedded ConnectJDBC driver for MS SQL Server (XA)

    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.

    The ConnectJDBC provider supports the following data source:
     com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource.
    
    Requires JDBC driver files:
    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.

    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.

    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.

    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).
  5. DataDirect SequeLink type 3 JDBC driver for MS SQL Server -- Deprecated

    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.

    DataDirect SequeLink type 3 JDBC driver supports the following data source:
     com.ddtek.jdbcx.sequelink.SequeLinkDataSource
    
    Requires JDBC driver files:
     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.)
    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.
    • enable2phase This property is necessary only if your application must participate in two-phase transactions. By default, Application Server sets a user-defined implementation type to a connection pool data source. The connection pool data source supports only one-phase transactions. Configure two-phase transaction support by setting the enable2Phase custom property on each data source that you create with your user-defined JDBC provider. Follow these steps:
      1. Go to the Custom properties administrative console page by clicking Resources > JDBC Providers > your_JDBC_provider > Data sources > your_data_source > Custom properties.
      2. Click New.
      3. Input enable2Phase as the property name and assign it the value of true. For Version 4 data sources, use a property that works in the opposite manner: Input disable2Phase and assign it the value of false.

    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.

  6. Microsoft JDBC driver for MS SQL Server 2000 -- Deprecated

    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.

    Microsoft JDBC driver for MS SQL Server 2000 supports the following 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.
    • enable2phase This property is necessary only if your application must participate in two-phase transactions. By default, Application Server sets a user-defined implementation type to a connection pool data source. The connection pool data source supports only one-phase transactions. Configure two-phase transaction support by setting the enable2Phase custom property on each data source that you create with your user-defined JDBC provider. Follow these steps:
      1. Go to the Custom properties administrative console page by clicking Resources > JDBC Providers > your_JDBC_provider > Data sources > your_data_source > Custom properties.
      2. Click New.
      3. Input enable2Phase as the property name and assign it the value of true. For Version 4 data sources, use a property that works in the opposite manner: Input disable2Phase and assign it the value of false.



Related concepts
Data sources
Resource adapters
JDBC providers
Related tasks
Configuring a JDBC provider and data source
Configuring a JDBC provider using the administrative console
Configuring a data source using the administrative console
Creating and configuring a JDBC provider and data source using the Java Management Extensions API
Related information
WebSphere Application Server Supported hardware and software
DB2 product Web pages
DB2 for z/OS product Web pages
Information Management Software for z/OS Solutions Information Center
DB2 for iSeries product Web pages
DB2 Universal Database for iSeries support pages
IBM Cloudscape version 5.1.x publications center
[Version 6.0.2] IBM Cloudscape version 10.0 information center
IBM Informix product family Web pages
Backward Compatibility for MS SQL Server components
FTP site for MS SQL Server-side JDBC driver updates
Reference topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rdat_minreq.html

© Copyright IBM Corporation 2002, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)