[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:

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



Searchable topic ID:   minreq
Last updated: Jun 21, 2007 4:12:58 PM CDT    WebSphere Application Server Express, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.exp.doc/info/exp/ae/rdat_minreq.html

Library | Support | Terms of Use | Feedback