[Version 5.0.2 and later]Vendor-specific data sources minimum required settings

The following list contains descriptions for every JDBC provider that can be defined for use with WebSphere Application Server Versions 5.x and 5.1.x. It also shows the supported data source classes and their required properties.

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

Use this list to find the provider information:

DB2

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

    The DB2 for z/OS JDBC Provider (RRS) is for use with the DB2 for 390 and z/OS Legacy JDBC Driver. It can be used only with WebSphere Application Server for z/OS. This provider supports the creation of WebSphere Application Server for z/OS v5.0 and v4.0 datasources. It also uses z/OS Resource Recovery Services (RRS) to coordinate transactions across multiple resource managers using two-phase commit processing.

    The DB2 for z/OS Local JDBC Provider (RRS) allows applications to use both JDBC and Structured Query Language in Java (SQLJ) access to DB2 databases. Use of SQLJ with Container Managed Persistence (CMP) is not supported under this provider.

    To use this provider, the legacy DB2 for z/OS JDBC Driver must be installed and configured to the WebSphere Application Server. Refer to the topic Using a DB2 for zOS Local JDBC Provider (RRS) with WebSphere Application Server for z/OS.

    The following configuration information is provided in a template for the DB2 for z/OS Local JDBC Provider (RRS), and is automatically filled in when you select this provider.

    The driver supports data source implementation:

    com.ibm.db2.jcc.DB2ConnectionPoolDataSource
    This DB2 data source implementation class enables RRS to run under WebSphere Application Server for z/OS, and allows WebSphere Application Server for z/OS to perform connection pooling. Note that when you configure the data source, you must specify a name for the data source definition.

    This provider requires JDBC driver files:

    • db2j2classes.zip, which are DB2 for z/OS Legacy JDBC driver files. They can be retrieved using the following class path:
      ${DB2390_JDBC_DRIVER_PATH}/classes/db2j2classes.zip
    • The native files (.so type files) required by the DB2 for OS/390 and z/OS Legacy JDBC driver, retrievable from the following library path:
      ${DB2390_JDBC_DRIVER_PATH}/lib

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.DB2DataStoreHelper

    It also requires a valid authentication alias. When res-auth = CONTAINER is used, however, it is permissible to not specify any authentication alias. In this case, the user identity associated with a connection created by the data source is the user identity associated with the current thread at the time a connection request is made.

    This driver requires the following properties:

    • databaseName The location name of the target database, used when establishing connections using this data source.

    Note: DB2 supports additional connection properties for the DB2 for 390 and z/OS Legacy JDBC Driver; set them as custom properties on the data source. For information about these optional data source properties, consult the Application Programming Guide and Reference for Java for your version of DB2 for z/OS.

  2. DB2 Universal JDBC Provider

    The DB2 Universal JDBC Provider is a non-XA JDBC provider that uses the DB2 Universal JDBC Driver to provide access to DB2 databases. The Universal JDBC Driver supports Java communication-based connectivity (driver Type 4), which allows distributed access to DB2. Additionally, the driver supports Java Native Interface (JNI) based connectivity (driver Type 2), which allows local access to DB2.

    Note: Under WebSphere Application Server for z/OS, driver Type 4 access to DB2 is supported only for connectivity to DB2 for z/OS (Version 7 and up) databases on the z/OS platform.

    The DB2 Universal JDBC Provider allows applications to use both JDBC and Structured Query Language in Java (SQLJ) access to DB2 databases. SQLJ use with CMP is also supported.

    To use this provider, you must have the DB2 Universal JDBC Driver for DB2 Version 7 or DB2 Version 8 installed and configured for WebSphere Application Server for z/OS. Refer to the topic Using a DB2 Universal JDBC Driver to access DB2 for z/OS.

    The following configuration information is provided in a template for the DB2 Universal JDBC Provider and is automatically filled in when you select this provider.

    The driver supports data source implementation:

    com.ibm.db2.jcc.DB2ConnectionPoolDataSource
    Note that when you configure the data source, you must specify a name for the data source definition. This data source implementation class performs only one-phase commit processing, except where driver Type 2 is specified in WebSphere Application Server for z/OS. In this case, RRS coordinates transaction processing and two-phase commit processing is performed for global transactions.

    Requires JDBC provider files:

    • db2jcc.jar This is the DB2 Universal JDBC Driver jar file. After the DB2 installation, this jar file is located in DB2's install directory. The fully-qualified path of this jar must be specified as the value of the DB2UNIVERSAL_JDBC_DRIVER_PATH environment variable. Class path:
      ${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar
      
    • db2jcc_license_cu.jar This is the DB2 Universal JDBC driver license file that allows access to DB2 Universal databases under Cloudscape and workstations. It is not used for WebSphere Application Server for z/OS, but is included to make the provider definition common between WebSphere Application Server for z/OS and WebSphere Application Server Distributed. 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 DB2 Universal databases under Cloudscape, workstations, and z/OS. After you install DB2, this jar file appears in the same DB2 directory as db2jcc.jar. Class path:
      ${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cisuz.jar
    • The native files (.so type files) required by the DB2 Universal JDBC Driver in WebSphere Application Server for z/OS. They are located at library path:
      ${DB2UNIVERSAL_JDBC_DRIVER_NATIVEPATH}

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper

    It also requires a valid authentication alias if the driverType property (see properties below) is set to 4. If the driverType property is set to 2, a component-managed authentication alias must be specified to use the datasource with res-auth APPLICATION. In the case where driverType 2 is specified and the datasource is used with res-auth CONTAINER, you can specify a container-managed authentication alias; however, it is not required. If you do not specify a container-managed alias, the user identity associated with a connection created by the datasource will be the user identity associated with the current thread at the time the connection is obtained.

    This driver requires the following properties:

    • databaseName The location name of the target database, used when establishing connections using this datasource.
    • driverType The JDBC connectivity type used by the datasource. There are two permitted values: 2 and 4. If you want to use Universal JDBC Type 2 driver, set this value to 2. If you want to use Universal JDBC Type 4 driver, set this value to 4.
    • ServerName The TCP/IP address or host name for the Distributed Relational Database Architecture (DRDA) server. This is required only if your driverType is set to 4. This property is not required for a driverType of 2.
    • portNumber The TCP/IP port number where the DRDA server resides. Specify a value only if your driverType is set to 4. This property is not required for a driverType of 2.

    Note: DB2 supports additional connection properties for the DB2 Universal JDBC Driver; set them as custom properties on the data source. For information about these optional data source properties, consult the Application Programming Guide and Reference for Java for your version of DB2 for z/OS.

  3. DB2 Universal JDBC Provider (XA)

    This provider is the XA DB2 Universal JDBC Provider that uses the DB2 Universal JDBC Driver to provide access to DB2 databases. The Universal JDBC Driver supports Java communication-based connectivity (driver Type 4), which allows distributed access to DB2. The driver also supports Java Native Interface (JNI) based connectivity (driver type 2), which allows local access to DB2. For XA capabilities, however, driver type 2 is not supported by the DB2 Universal JDBC Driver on WebSphere Application Server for z/OS. Therefore driver type 2 should not be used when defining an XA data source under this provider.

    Note: Under WebSphere Application Server for z/OS, driver type 4 access to DB2 is supported only for connectivity to DB2 for z/OS (Version 7 and up) on the z/OS platform.

    The J2EE XA transaction architecture is supported by the universal JDBC driver under this provider. This permits the coordination of global transactions across multiple resource managers using two-phase commit processing. The driver also supports one-phase transaction processing under this provider.

    The DB2 Universal JDBC Provider (XA) allows applications to use both JDBC and Structured Query Language in Java (SQLJ) access to DB2 databases. SQLJ use with CMP is also supported.

    This provider supports only the creation of WebSphere Application Server for z/OS v5.0 datasources. The creation of 4.0 datasources is not supported.

    To use this provider, you must have the DB2 Universal JDBC Driver for DB2 Version 7 or DB2 Version 8 installed and configured for WebSphere Application Server for z/OS, or you must have the z/OS Application Connectivity to DB2 for z/OS feature installed and configured for WebSphere Application Server for z/OS. Refer to the topic Using a DB2 Universal JDBC Driver to access DB2 for z/OS.

    The following configuration information is provided in a template for the DB2 Universal JDBC Provider (XA) and is automatically filled in when you select this provider.

    The driver supports data source implementation:

    com.ibm.db2.jcc.DB2XADataSource
    This implementation class, of course, supports J2EE XA transaction processing. Note that when you configure the data source, you must specify a name for the data source definition.

    This provider requires JDBC driver files:

    • db2jcc.jar This is the DB2 Universal JDBC Driver jar file. After the DB2 installation, this jar file is located in DB2's install directory. The fully-qualified path of this jar must be specified 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 DB2 Universal databases under Cloudscape and workstations. It is not used for WebSphere Application Server for z/OS, but is included to make the provider definition common between WebSphere Application Server for z/OS and WebSphere Application Server Distributed. 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 DB2 Universal databases under Cloudscape, workstations, and z/OS. After you install DB2, this jar file appears in the same DB2 directory as db2jcc.jar. Class path:
      ${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cisuz.jar
    • The native files (.so type files) required by the DB2 Universal JDBC Driver in WebSphere Application Server for z/OS. They can be found at library path:
      ${DB2UNIVERSAL_JDBC_DRIVER_NATIVEPATH}
      (In cases that do not require native files, set the DB2UNIVERSAL_JDBC_DRIVER_NATIVEPATH to null.)

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper

    It also requires a valid authentication alias.

    The driver requires the following properties:

    • databaseName The location name of the target database, used when establishing connections using this data source.
    • driverType The JDBC connectivity type used by the datasource. For WebSphere Application Server for z/OS, use only driverType 4. Use of driverType 2 is not supported.
    • serverName The TCP/IP address or host name for the Distributed Relational Database Architecture (DRDA) server.
    • portNumber The TCP/IP port number where the DRDA server resides.

    Note: DB2 supports additional connection properties for the DB2 Universal JDBC Driver; set them as custom properties on the data source. For information about these optional data source properties, consult the Application Programming Guide and Reference for Java for your version of DB2 for z/OS.

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  

    This provider requires JDBC driver files: db2j.jar. (This file ships with WebSphere Application Server. If you are running Cloudscape Version 5.1, you can find this file in the WAS_HOME/cloudscape/lib directory).

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper

    This driver does not require a valid authentication alias.

    It requires the following properties:

    • 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 

    This provider requires JDBC driver files: db2j.jar (This file ships with WebSphere Application Server. If you are running Cloudscape Version 5.1, you can find this file in the WAS_HOME/cloudscape/lib directory).

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper

    This driver does not require a valid authentication alias.

    It requires the following properties:

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

  3. [Version 5.0.2 and later]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

    This provider 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}/otherJars/db2jcc.jar</classpath>
      
      <classpath>${CLOUDSCAPE_JDBC_DRIVER_PATH}/db2j.jar</classpath>
      
      <classpath>${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar</classpath>
      
      which means that the db2jcc.jar from DB2 always takes precedence. Note that this also means that you must set the DB2 environment variable DB2UNIVERSAL_JDBC_DRIVER_PATH in WebSphere when you set up your DB2 datasource. This is instead of hard coding the path of the db2jcc.jar for DB2 datasources.
    • db2jcc_license_cu.jar This file is the DB2 Universal JDBC license file that provides access to the Cloudscape databases using the Network Server framework. Use this file to gain access to the database. This file ships with WebSphere and is located in ${UNIVERSAL_JDBC_DRIVER_PATH}.

      Note: UNIVERSAL_JDBC_DRIVER_PATHis a WebSphere environment variable that is already defined to the location in Websphere Application Server where the license jar file above is located, and will only be used if the DB2UNIVERSAL_JDBC_DRIVER_PATH is not set. DB2 users should ensure that DB2UNIVERSAL_JDBC_DRIVER_PATH is set to avoid loading multiple vesions of the db2jcc.jar file.

      Note: DB2UNIVERSAL_JDBC_DRIVER_PATH is a WebSphere environment variable that you must set to point to the location of db2jcc.jar file (that comes with DB2). This variable is set only if you create a db2 provider. See the DB2 section for more information on the DB2UNIVERSAL_JDBC_DRIVER_PATH path variable.

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

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.CloudscapeNetworkServerDataStoreHelper

    Note: The administrative console incorrectly lists the DB2UniversalDataStoreHelper as the default value for the DataStoreHelper class. You must change the default value to com.ibm.websphere.rsadapter.CloudscapeNetworkServerDataStoreHelper. Also change the custom properties, using the instructions in the customer property section.

    This driver also requires a valid authentication alias.

    It requires the following properties:

    • 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 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 on IBM Cloudscape, visit the Cloudscape Web site at: http://www.ibm.com/software/data/cloudscape/

Informix

  1. Informix JDBC Provider

    The Informix JDBC Driver is a Type 4 JDBC driver that provides JDBC access to the Informix database.

    Informix JDBC Driver supports one phase data source:

     com.informix.jdbcx.IfxConnectionPoolDataSource

    This provider requires JDBC driver files:

       ifxjdbc.jar
       ifxjdbcx.jar
    

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.InformixDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

    • 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 Provider (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

    This provider requires JDBC driver files:

       ifxjdbc.jar
       ifxjdbcx.jar
    

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.InformixDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

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

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

    Sybase JDBC Driver supports one phase data source:

    com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource 
    

    This provider requires JDBC driver files: jconn2.jar.

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.SybaseDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

    • serverName The name of the database server. Example: myserver.mydomain.com.
    • [Version 5.0.1 and later] 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 Provider (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 

    This provider requires JDBC driver files: jconn2.jar.

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.SybaseDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

    • serverName The name of the database server. Example: myserver.mydomain.com
    • [Version 5.0.1 and later] 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 Provider -- 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
    

    This provider requires JDBC driver files: jconn2.jar.

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.SybaseDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

    • serverName The name of the database server. Example: myserver.mydomain.com
    • [Version 5.0.1 and later] 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 Provider (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
    

    This provider requires JDBC driver files: jconn2.jar.

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.SybaseDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

    • serverName The name of the database server. Example: myserver.mydomain.com
    • [Version 5.0.1 and later] 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 Provider

    The Oracle JDBC Driver provides JDBC access to the Oracle database. This JDBC driver supports both Type 2 JDBC access and Type 4 JDBC access.

    Oracle JDBC Driver supports one phase data source:

     oracle.jdbc.pool.OracleConnectionPoolDataSource
    

    This provider requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.OracleDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

    • 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 Provider (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
    

    This provider requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.OracleDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

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

  3. Oracle JDBC Thin Provider -- 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

    This provider requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.OracleDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

    • 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 Provider (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
    

    This provider requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.OracleDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

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

    This provider requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.OracleDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

    • 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 Provider (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
    

    This provider requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar.)

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.OracleDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

    • 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. This provider is for use only with the ConnectJDBC driver purchased from DataDirect Technologies.

    This JDBC provider supports this data source:

     com.ddtek.jdbcx.sqlserver.SQLServerDataSource

    It requires JDBC driver files:

    sqlserver.jar,
    base.jar and util.jar
    
    (The spy.jar file is optional. You need this file to enable spy logging. The spy.jar file is not in the same directory as the other three jar files. Instead, it is located in the ../spy/ directory.)

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

    • 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. This provider is for use only with the ConnectJDBC driver purchased from DataDirect Technologies.

    This JDBC provider supports this data source:

    com.ddtek.jdbcx.sqlserver.SQLServerDataSource.
    

    It requires JDBC driver files:

    sqlserver.jar,
    base.jar and util.jar.
    
    (The spy.jar file is optional. You need this file to enable spy logging. The spy.jar file is not in the same directory as the other three jar files. Instead, it is located in the ../spy/ directory.)

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

    • 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. 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 is for use only with the SequelLink type 3 JDBC driver purchased from DataDirect Technologies.

    This JDBC provider supports the data source:

     com.ddtek.jdbcx.sequelink.SequeLinkDataSource
    

    This provider requires JDBC driver files:

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

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.SequeLinkDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

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

  4. 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 that provides XA-compliant JDBC access to MS SQL Server via the SequeLink server. This JDBC driver provider is for use only with the SequelLink type 3 JDBC driver purchased from DataDirect Technologies

    This JDBC provider supports the data source:

    com.ddtek.jdbcx.sequelink.SequeLinkDataSource
    

    This provider requires JDBC driver files:

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

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.SequeLinkDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

    • 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/software/websphere/info/tools/DataDirect/datadirect.htm
    
    

    For more information on the DataDirect SequeLink type 3 JDBC driver, visit the DataDirect Web site at:

    http://www.datadirect-technologies.com/
    
    

  5. [Version 5.0.1 and later]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
    

    This provider requires JDBC driver files:

    mssqlserver.jar,
    msbase.jar and msutil.jar
    
    (The spy.jar file is optional. You need it to enable spy logging. However, Microsoft does not ship the spy.jar file. Contact Microsoft about this issue.)

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

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

  6. [Version 5.0.1 and later]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
    

    This provider requires JDBC driver files:

    mssqlserver.jar,
    msbase.jar and msutil.jar
    
    (The spy.jar file is optional. You need it to enable spy logging. However, Microsoft does not ship the spy.jar file. Contact Microsoft about this issue.)

    The driver requires DataStoreHelper class:

    com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper

    It also requires a valid authentication alias.

    This driver requires the following properties:

    • 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


Related concepts
Data sources
Resource adapter
JDBC providers
Related tasks
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



Searchable topic ID:   minreq
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/rdat_minreq.html

Library | Support | Terms of Use | Feedback