Vendor-specific data sources minimum required settings

 

Contents

  1. DB2
  2. DB2 UDB for iSeries
  3. DB2 for z/OS
  4. Cloudscape
  5. Informix
  6. Sybase
  7. Oracle
  8. MS SQL Server

 

Overview

This document contains descriptions for every JDBC provider supported in WAS Versions 5.0, 5.0.1, and 5.0.2. It also shows the supported data source classes and their required properties.

Specific fields are designated for the user and password properties. Inclusion of a property in the list does not imply that add it to the data source properties list. Rather, inclusion in the list means that a value is typically required for that field.

 

DB2

  1. DB2 Universal JDBC Driver Provider

    The DB2 Universal JDBC Driver is an architecture-neutral JDBC driver for distributed and local DB2 access that supports both Type 2 and Type 4 JDBC drivers. To use the Type 4 driver, install DB2 Version 8.1 or a later. To use the Type 2 driver, install DB2 Version 8.1 Fix Pack 2 or a later version.

    This driver only supports one phase transactions using the following data source...

    com.ibm.db2.jcc.DB2ConnectionPoolDataSource

    This JDBC driver allows applications to use both JDBC and SQL in Java (SQLJ) access.

    Requires the following JDBC driver files:

    db2jcc.jar Set...

    DB2UNIVERSAL_JDBC_DRIVER_PATH
    ...to point to db2jcc.jar file.

    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.

    To get version: 

    java com.ibm.db2.jcc.DB2Jcc -version
    db2jcc_license_cu.jar 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...

    $WAS_HOME/universalDriver/lib
    db2jcc_license_cisuz.jar License file that allows access to the following databases:

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

    Set the DB2UNIVERSAL_JDBC_DRIVER_PATH env variable to point to the db2jcc_license_cisuz.jar file.

    Requires DataStoreHelper class... 

    com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

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

    Architecture-neutral JDBC driver for distributed and local DB2 access. To use this driver, install DB2 Version 8.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 Found in the DB2 java directory. Set the DB2UNIVERSAL_JDBC_DRIVER_PATH environment variable to point to db2jcc.jar file.

      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.

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

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

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

      $WAS_HOME/universalDriver/lib

    • 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
    If you use this driver provider to connect to DB2 for z/OS, change the data store helper class to 

    com.ibm.websphere.rsadapter.DB2390DataStoreHelper

    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. The only permitted value is 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.

    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.

    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.

  5. DB2 JDBC Provider -- Deprecated

    This JDBC provider is the same as the DB2 Legacy CLI-based Type 2 JDBC Driver. This JDBC driver is deprecated. Use the DB2 Legacy CLI-based Type 2 JDBC Driver instead of this one.

    DB2 JDBC Provider supports one phase data source 

    COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource

    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 JDBC Provider (XA) -- Deprecated

    This JDBC provider is the same as the DB2 Legacy CLI-based Type 2 JDBC Driver (XA). This JDBC driver is deprecated. Use the DB2 Legacy CLI-based Type 2 JDBC Driver (XA) instead of this one.

    DB2 JDBC Provider (XA) supports two phase data source 

    COM.ibm.db2.jdbc.DB2XADataSource

    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.

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

For information on configuring WebSphere Application Server for DB2 access, see Configuring DB2 article.

 

DB2 UDB for iSeries

  1. DB2 UDB for iSeries (Native - Version 5 Release 2 and later)

    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 - Version 5 Release 2 and later)

    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 (Native - Version 5 Release 1 and earlier)

    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.

    The V5R1 and earlier JDBC drivers, although still supported, will receive no further enhancements. We recommend that you replace them with the V5R2 JDBC driver providers.

  4. DB2 UDB for iSeries (Native XA - Version 5 Release 1 and earlier)

    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.

    The V5R1 and earlier JDBC drivers, although still supported, will receive no further enhancements. We recommend that you replace them with the V5R2 JDBC driver providers.

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

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

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

 

DB2 for z/OS

  1. DB2 for z/OS JDBC Provider

    The DB2 for z/OS JDBC Provider provides remote JDBC access to DB2 for z/OS. The DB2 for z/OS JDBC Provider provides remote JDBC access to DB2 on z/OS. This is the Legacy CLI-based JDBC driver. You cannot use this driver locally on DB2 z/OS. Use the DB2 for z/OS Local JDBC Provider (RRS) on local z/OS systems. You cannot see this JDBC Provider on the JDBC Provider drop down list in the administrative console. To create DB2 for z/OS data sources, use the DB2 Legacy CLI-based Type 2 JDBC Driver instead of this one, and change the DataStoreHelper class to com.ibm.websphere.rsadapter.DB2390DataStoreHelper.

    DB2 for z/OS JDBC provider supports one phase data source 

    COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource

    Requires JDBC driver files: db2java.zip

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2390DataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

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

  2. DB2 for z/OS JDBC Provider (XA)

    The DB2 for z/OS JDBC Provider provides remote XA-compliant JDBC access to DB2 for z/OS. The DB2 for z/OS JDBC Provider provides remote JDBC access to DB2 on z/OS. This is the Legacy CLI-based JDBC driver. You cannot use this driver locally on DB2 z/OS. Use the DB2 for z/OS Local JDBC Provider (RRS) on local z/OS systems. You cannot see this JDBC Provider on the JDBC Provider drop down list in the administrative console. To create DB2 for z/OS XA data sources, use the DB2 Legacy CLI-based Type 2 JDBC Driver (XA) instead of this one, and change the DataStoreHelper class to com.ibm.websphere.rsadapter.DB2390DataStoreHelper.

    DB2 for z/OS JDBC (XA) provider supports two phase data source 

    COM.ibm.db2.jdbc.DB2XADataSource

    Requires JDBC driver files: db2java.zip

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2390DataStoreHelper

    Requires a valid authentication alias.

    Requires properties:

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

  3. DB2 for z/OS Local JDBC Provider (RRS)

    The DB2 for z/OS JDBC Provider provides local JDBC access to DB2 for z/OS. The DB2 for z/OS Local JDBC Provider provides local JDBC access to DB2 on z/OS. This provider uses the native z/OS Resource Recovery Services (RRS) transaction manager to handle two-phase commit transactions. You cannot see this JDBC Provider on the JDBC Provider drop down list in the administrative console. This JDBC Provider is only used when accessing local databases in the z/OS system. Currently this JDBC Provider is notonly supported in WAS for z/OS.

    DB2 for z/OS Local JDBC provider supports two phase data source 

    COM.ibm.db2.jcc.DB2ConnectionPoolDataSource

    Requires JDBC driver files: db2j2classes.zip

    Requires DataStoreHelper class 

    com.ibm.websphere.rsadapter.DB2390LocalDataStoreHelper

    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. 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 JDBC driver files: db2j.jar. (This file ships with WebSphere Application Server. If you are running Cloudscape Version 5.1, you can find this file in the WAS_HOME/cloudscape/lib directory).

    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. Example: Sample.

  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 JDBC driver files: db2j.jar (This file ships with WebSphere Application Server. If you are running Cloudscape Version 5.1, you can find this file in the WAS_HOME/cloudscape/lib directory).

    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. Example: Sample or c:\sample.

  3. 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. 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, 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>${WAS_INSTALL_ROOT}/universalDriverForCloudscape/db2jcc.jar</classpath><classpath>${CLOUDSCAPE51_JDBC_DRIVER_PATH}/db2j.jar</classpath>
<classpath>${CLOUDSCAPE51_JDBC_DRIVER_PATH}/db2jcc_license_c.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 that 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 and the list of Cloudscape attributes. Example: c:\sample;create=true.

    • driverType Only the Type 4 driver is allowed.

    • serverName The TCP/IP address or the host name for the 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/

 

Databases-IBM Cloudscape Marginalia

  1. Descriptive error messages
  2. driverType data source custom property
  3. Uninstall Cloudscape v5.1.x
  4. DB2 JDBC settings instead of Cloudscape
  5. Accessing the result set after a transaction is committed
  6. Remove "export" keywords to support Cloudscape tools on Solaris

 

No descriptive errors

When running WAS V5.0.2 against the Cloudscape Network Server or the DB2 universal driver, you cannot see the descriptive error messages from the database unless the retrieveMessagesFromServerOnGetMessage data source custom property is set to true. By default, the full message text is not returned to the client when a server-side error occurs. This property is disabled by default.

 

driverType data source with Network Server framework

When running WAS V5.0.2 with Cloudscape using the Network Server framework, you can receive the following exception if you either forget to set the driverType data source custom property or set it to 2

com.ibm..db2.jcc.b.SQLException: Unexpected throwable caught java.lang.UnsatisfiedLinkError: DBConnect

To avoid receiving the exception, set the driverType data source custom property to 4.

 

DB2 JDBC settings instead of Cloudscape

When creating a new Cloudscape JDBC Provider Network Server using the universal JDBC driver provider through the console in WAS v5.0.2, the console fills in the DB2 universal data sources settings by default instead of the Cloudscape Network Server ones. Those settings include:

  1. the DataStoreHelper class

  2. the data source custom properties

The incorrect settings do not include the implementation class, which is just like the DB2 Universal one.

If you want to create the Cloudscape JDBC Provider Network Server using the universal JDBC driver provider, perform the following steps to manually modify the entries in the console:

  1. Change the DataStoreHelper class to 

    com.ibm.websphere.rsadapter.CloudscapeNetworkServerDataStoreHelper

  2. You only need the following custom properties

    driverType 4 (Only valid value for Network Server)
    serverName Server TCP/IP address or name. Required
    databaseName Database name
    retrieveMessagesFromServerOnGetMessage Required by WAS, not the database. Defaults to false by the database. Must be set to true in WAS.

    The following data source custom properties are optional

    portNumber. Port number where Network Server listens for connection requests. Required. Default is port 1527.
    logWriter
    traceLevel
    traceFile
    traceFileAppend
    deferPrepares Works as documented except that the prepare on EXECUTE STATEMENT is never deferred
    resultSetHoldability Defaults to CLOSE_CURSORS_AT_COMMIT for Cloudscape. This is the only valid value for Network Server. Use the JDBC 3.0 API's for setting holdability.
    securityMechanism Network Server supports the following security Mechanisms.

    com.ibm.db2.jcc.DB2BaseDataSource.CLEAR_TEXT_PASSWORD_SECURITY
    com.ibm.db2.jcc.DB2BaseDataSource.ENCRYPTED_PASSWORD_SECURITY

 

Accessing the result set after a transaction is committed

When you run WAS with Cloudscape using the Cloudscape network server framework, Cloudscape throws an exception when you access the result set after the transaction is committed despite the fact that the cursor holdability is false by default.

This problem does not exist when you run in Cloudscape embedded. As this problem has been reported to Cloudscape, you can consult Cloudscape Support.

Ensure that your application does not rely on an exception that is thrown.

 

Remove "export" keywords to support Cloudscape tools on Solaris

Cloudscape tools, for example, ij.sh, cview.sh, sysinfo.sh, startNetworkserver.sh, and stopNetworkserver.sh might not work on the Solaris Operating Environment.

The scripts contain a keyword that is not compatible with the Solaris Operating Environment.

Change the scripts to remove the "export" keyword as indicated in the following example:

Change...

export xyz = abc

...to...

xyz = abc

 

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 The physical name of the database server. 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.

  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 The physical name of the database server. 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

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

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

  3. Sybase 12.0 JDBC Driver -- Deprecated

    This JDBC Driver provider is the same as Sybase JDBC Driver. This JDBC driver is deprecated. Use Sybase JDBC Driver instead of this one.

    Sybase 12.0 JDBC Driver supports one phase data source 

     com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource

    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.

  4. Sybase 12.0 JDBC Driver (XA) -- Deprecated

    This JDBC Driver provider is the same as Sybase JDBC Driver (XA). This JDBC driver is deprecated. Use the Sybase JDBC Driver (XA) instead of this one.

    Sybase 12.0 JDBC Driver (XA) supports two phase data source 

    com.sybase.jdbc2.jdbc.SybXADataSource

    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.

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

 

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

    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:@servername:1521:myDatabase, where servername 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

    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:@servername:1521:myDatabase, where servername is the server name, 1521 is the port it is using for communication, and myDatabase is the database name.

  3. Oracle JDBC Thin Driver -- Deprecated

    Both the Oracle JDBC Thin Driver and the Oracle JDBC oci8 Driver are deprecated. Use the Oracle JDBC Driver instead of these two.

    Oracle JDBC Thin Driver is a Type 4 JDBC driver that provides JDBC access to the Oracle database. Oracle JDBC Thin Driver is deprecated. Use the Oracle JDBC Driver instead of this one.

    Oracle JDBC Thin Driver supports one phase data source 

     oracle.jdbc.pool.OracleConnectionPoolDataSource

    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:@localhost:1521:sample for thin driver and jdbc:oracle:oci8:@sample for thick driver, where localhost is the server name, 1521 is the port it is using for communication, and sample is the database name.

  4. Oracle JDBC Thin Driver (XA) -- Deprecated

    Both the Oracle JDBC Thin Driver (XA) and the Oracle JDBC oci8 Driver (XA) are deprecated. Use the Oracle JDBC Driver (XA) instead of these two.

    Oracle JDBC Thin Driver (XA) is a Type 4 JDBC driver that provides XA-compliant JDBC access to the Oracle database. Oracle JDBC Thin Driver (XA) is deprecated. Use the Oracle JDBC Driver (XA) instead of this one.

    Oracle JDBC Thin Driver (XA) supports two phase data source 

     oracle.jdbc.xa.client.OracleXADataSource

    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:@localhost:1521:sample for thin driver and jdbc:oracle:oci8:@sample for thick driver, where localhost is the server name, 1521 is the port it is using for communication, and sample is the database name.

  5. Oracle JDBC oci8 Driver -- Deprecated

    Both the Oracle JDBC Thin Driver and the Oracle JDBC oci8 Driver are deprecated. Use the Oracle JDBC Driver instead of these two.

    Oracle JDBC oci8 Driver is a Type 2 JDBC driver that provides JDBC access to the Oracle database. Oracle JDBC oci8 Driver is deprecated. Use the Oracle JDBC Driver instead of this one.

    Oracle JDBC oci8 Driver supports one phase data source 

    oracle.jdbc.pool.OracleConnectionPoolDataSource

    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:@localhost:1521:sample for thin driver and jdbc:oracle:oci8:@sample for thick driver, where localhost is the server name, 1521 is the port it is using for communication, and sample is the database name.

  6. Oracle JDBC oci8 Driver (XA) -- Deprecated

    Both the Oracle JDBC Thin Driver (XA) and the Oracle JDBC oci8 Driver (XA) are deprecated. Use the Oracle JDBC Driver (XA) instead of these two.

    Oracle JDBC oci8 Driver (XA) is a Type 2 JDBC driver that provides XA-compliant JDBC access to the Oracle database. Oracle JDBC oci8 Driver (XA) is deprecated. Use the Oracle JDBC Driver (XA) instead of this one.

    Oracle JDBC oci8 Driver (XA) supports two phase data source 

     oracle.jdbc.xa.client.OracleXADataSource

    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:@localhost:1521:sample for thin driver and jdbc:oracle:oci8:@sample for thick driver, where localhost is the server name, 1521 is the port it is using for communication, and sample is the database name.

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

 

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 database. Only use this provider for the ConnectJDBC driver purchased from DataDirect Technologies. Do not use it with the Connect JDBC driver embedded in WebSphere.

    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 which provides XA-compliant JDBC access to the MS SQL Server database. Only use this provider for the ConnectJDBC driver purchased from DataDirect Technologies. Do not use it with the Connect JDBC driver embedded in WebSphere.

    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/

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

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

    To view the instructions for installing Stored Procedures for JTA (required when enabling two-phase commit) on the WebSphere CD, refer to the following FTP site 

    How to install "Stored Procedures for JTA" from the WebSphere CD

    You can download the latest patches and upgrades to the WebSphere embedded ConnectJDBC drivers from the following FTP site 

    ftp://ftp.software.ibm.com/softwa../WAS51/info/tools/DataDirect/datadirect.htm

  5. DataDirect SequeLink type 3 JDBC driver for MS SQL Server

    DataDirect SequeLink type 3 JDBC driver for MS SQL Server is a Type 3 JDBC driver that provides JDBC access to MS SQL Server via SequeLink server. This JDBC driver provider supports both the SequeLink type 3 JDBC driver shipped with WebSphere Application Server and the SequeLink type 3 JDBC driver purchased from DataDirect.

    This JDBC provider supports this data source 

     com.ddtek.jdbcx.sequelink.SequeLinkDataSource

    Requires JDBC driver files 

     sljc.jar and
 spy-sl53.jar
    (The JDBC driver shipped with WAS requires the sljc.jar and the spy-sl53.jar files. The JDBC driver purchased from DataDirect requires the sljc.jar and the spy.jar files. The spy.jar and spy-sl35.jar files are optional. You need these files to enable spy logging.)

    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.

  6. DataDirect SequeLink type 3 JDBC driver for MS SQL Server (XA)

    DataDirect SequeLink type 3 JDBC driver for MS SQL Server (XA) is a Type 3 JDBC driver which provides XA-compliant JDBC access to MS SQL Server via the SequeLink server. This JDBC driver provider supports both the SequeLink type 3 JDBC driver shipped with WAS and the SequeLink type 3 JDBC driver purchased from DataDirect.

    This JDBC provider supports this data source 

    com.ddtek.jdbcx.sequelink.SequeLinkDataSource

    Requires JDBC driver files 

     sljc.jar and
spy-sl53.jar
    (The JDBC driver shipped with WAS requires the sljc.jar and the spy-sl53.jar files. The JDBC driver purchased from DataDirect requires the sljc.jar and the spy.jar files. The spy.jar and spy-sl35.jar files are optional. You need these files to enable spy logging.)

    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.

    To view instructions for installing SequeLink Server from the WebSphere CD, refer to this FTP site 

    How to install SequeLink Server from the WebSphere CD
    Only install the SequeLink server from the WebSphere CD if you are using the SequeLink JDBC driver embedded in WebSphere. Otherwise, install the SequeLink server purchased from DataDirect Technologies.

    You can download the latest patches and upgrades to the WebSphere embedded SequeLink type 3 JDBC drivers from the following FTP site 

    ftp://ftp.software.ibm.com/softwa../WAS51/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/

  7. Microsoft JDBC driver for MSSQLServer 2000

    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.

  8. Microsoft JDBC driver for MSSQLServer 2000 (XA)

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

    This JDBC provider supports this data source 

    com.microsoft.jdbcx.sqlserver.SQLServerDataSource

    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
Creating and configuring a data source using the administrative console
Creating and configuring a JDBC provider using the administrative console
Creating and configuring a JDBC provider and data source using the Java Management Extensions API