Vendor-specific data sources minimum required settings

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

Database type	JDBC Provider	Transaction support	Version and other considerations
DB2 on Windows, UNIX, or workstation-based LINUX	DB2 Universal JDBC Provider	One phase only
	DB2 Universal JDBC Provider (XA)	One and two phase	The XA implementation is not supported in WebSphere Application Server run on workstation-based LINUX.
	DB2 legacy CLI-based Type 2 JDBC Provider	One phase only
	DB2 legacy CLI-based Type 2 JDBC Provider (XA)	One and two phase
DB2 UDB for iSeries	DB2 UDB for iSeries (Native)	One phase only	Recommended for use with WebSphere Application Server run on iSeries
	DB2 UDB for iSeries (Native XA)	One and two phase	Recommended for use with WebSphere Application Server run on iSeries
	DB2 UDB for iSeries (Toolbox)	One phase only
	DB2 UDB for iSeries (Toolbox XA)	One and two phase
	DB2 Universal JDBC Provider (XA)	One and two phase	- Only for use with WebSphere Application Server run on z/OS - Only driver type 4 is supported - Does not support Version 4 data sources
	DB2 legacy CLI-based Type 2 JDBC Provider	One phase only	- Only for use with WebSphere Application Server run on Windows, UNIX, or workstation-based LINUX - Requires the DB2 Connect driver (available from DB2)
	DB2 legacy CLI-based Type 2 JDBC Provider (XA)	One and two phase	- Only for use with WebSphere Application Server run on Windows, UNIX, or workstation-based LINUX - Requires the DB2 Connect driver (available from DB2)
DB2 on z/OS	DB2 for z/OS Local JDBC Provider (RRS), using the Legacy DB2 for z/OS JDBC Driver	One and two phase	Only for use with WebSphere Application Server run on z/OS
	DB2 Universal JDBC Provider	One phase only
	DB2 Universal JDBC Provider (XA)	One and two phase	- Only driver type 4 is supported in WebSphere Application Server run on z/OS - Does not support Version 4 data sources in WebSphere Application Server run on z/OS
	DB2 legacy CLI-based Type 2 JDBC Provider	One phase only	- Only for use with WebSphere Application Server run on Windows, UNIX, or workstation-based LINUX - Requires the DB2 Connect program (available from DB2)
	DB2 legacy CLI-based Type 2 JDBC Provider (XA)	One and two phase	- Only for use with WebSphere Application Server run on Windows, UNIX, or workstation-based LINUX - Requires the DB2 Connect program (available from DB2)
Cloudscape	Cloudscape JDBC Provider	One phase only	- Not for use in clustered environment: accessible from a single JVM only - Does not support Version 4 data sources
	Cloudscape JDBC Provider (XA)	One and two phase	- Not for use in clustered environment: accessible from a single JVM only - Does not support Version 4 data sources
	Cloudscape Network Server Provider using the Universal JDBC driver	One phase only	- Can be used in clustered environment: a database instance can be accessed by multiple JVMs - Does not support XA - Does not support Version 4 data sources
Derby Restriction: Derby Version 10.0 cannot be used as a production database. Derby Version 10.0 can only be used for development and test purposes. No restriction: Derby Version 10.1 can be used in production environments as well as in development and test environments.	Derby JDBC Provider	One phase only	- Not for use in clustered environment: accessible from a single JVM only - Does not support Version 4 data sources
	Derby JDBC Provider (XA)	One and two phase	- Not for use in clustered environment: accessible from a single JVM only - Does not support Version 4 data sources
	Derby Network Server Provider using the Universal JDBC driver	One phase only	- Can be used in clustered environment: a database instance can be accessed by multiple JVMs - Does not support XA - Does not support Version 4 data sources
Informix	Informix JDBC Provider	One phase only
Informix	Informix JDBC Provider (XA)	One and two phase
Sybase	Sybase jConnect for JDBC Provider	One phase only
Sybase	Sybase jConnect for JDBC Provider (XA)	One and two phase
Oracle	Oracle JDBC Provider	One phase only
Oracle	Oracle JDBC Provider (XA)	One and two phase
MS SQL Server	DataDirect ConnectJDBC Provider, type 4 driver, for MS SQL Server	One phase only	Only for use with the corresponding driver from DataDirect Technologies
	DataDirect ConnectJDBC Provider, type 4 driver, for MS SQL Server (XA)	One and two phase	Only for use with the corresponding driver from DataDirect Technologies
	WebSphere embedded ConnectJDBC Provider for MS SQL Server	One phase only	Cannot be used outside of WebSphere Application Server environment
	WebSphere embedded ConnectJDBC Provider for MS SQL Server (XA)	One and two phase	Cannot be used outside of WebSphere Application Server environment

The following list contains the requirements for creating data sources with every JDBC provider type that is supported in WebSphere Application Server Version 6.x. Specific fields are designated for the user and password properties. Inclusion of a property in the list does not imply that you should add it to the data source custom properties list. Rather, inclusion in the list means that a value is typically required for that field.

Important: After you determine the type of JDBC provider that suits your application and environment, ensure that you acquire the corresponding JDBC driver at a release level supported by this version of WebSphere Application Server. Consult the Supported hardware and software Web page at the http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html IBM Web address. Use these links to find your provider and data source information:

The classpath for this provider is set as follows: <classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar </classpath> <classpath>${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar</classpath> <classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cisuz.jar</classpath>

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

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

The classpath for this provider is set as follows: <classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar </classpath> <classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar</classpath> <classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cisuz.jar</classpath>

<classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar</classpath> <classpath>${CLOUDSCAPE_JDBC_DRIVER_PATH}/db2j.jar</classpath> <classpath>${CLOUDSCAPE51_JDBC_DRIVER_PATH}/db2j.jar</classpath> <classpath>${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar</classpath>

<classpath>${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar</classpath> <classpath>${CLOUDSCAPE_JDBC_DRIVER_PATH}/otherJars/db2jcc.jar</classpath> <classpath>${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar</classpath>

Informix

Informix JDBC Driver
The Informix JDBC Driver is a Type 4 JDBC driver that provides JDBC access to the Informix database. Informix JDBC Driver supports one phase data source:
```
 com.informix.jdbcx.IfxConnectionPoolDataSource  
```
Requires JDBC driver files:
```
   ifxjdbc.jar  
   ifxjdbcx.jar 
```
Requires DataStoreHelper class:
```
com.ibm.websphere.rsadapter.InformixDataStoreHelper 
```
Requires a valid authentication alias. Requires properties:
- serverName The name of the Informix instance on the server. Example: ol_myserver.
- portNumber The port on which the instances listen. Example: 1526.
- ifxIFXHOST Either the IP address or the host name of the machine that is running the Informix database to which you want to connect. Example: myserver.mydomain.com.
  
  To support IPv6: On AIX and Solaris, IBM Informix Dynamic Server 10.00 with fix pack 1 supports the IPv6 standard. To enable IPv6 on your WebSphere Application Server connection with one of these Informix releases, input your full IPv6 host name for the ifxIFXHOST property.
- databaseName The name of the database from which the data source obtains connections. Example: Sample.
- informixLockModeWait Although not required, this property enables you to set the number of seconds that Informix software waits for a lock. By default, Informix code throws an exception if it cannot immediately acquire a lock. Example: 2.
Informix JDBC Driver (XA)
The Informix JDBC Driver (XA) is a Type 4 JDBC driver that provides XA-compliant JDBC access to the Informix database.
Informix JDBC Driver (XA) supports two phase data source:
```
com.informix.jdbcx.IfxXADataSource 
```
Requires JDBC driver files:
```
   ifxjdbc.jar 
   ifxjdbcx.jar 
```
Requires DataStoreHelper class:
```
com.ibm.websphere.rsadapter.InformixDataStoreHelper 
```
Requires a valid authentication alias. Requires properties:
- serverName The name of the Informix instance on the server. Example: ol_myserver.
- portNumber The port on which the instances listen. Example: 1526.
- ifxIFXHOST Either the IP address or the host name of the machine that is running the Informix database to which you want to connect. Example: myserver.mydomain.com.
  
  To support IPv6: On AIX and Solaris, IBM Informix Dynamic Server 10.00 with fix pack 1 supports the IPv6 standard. To enable IPv6 on your WebSphere Application Server connection with one of these Informix releases, input your full IPv6 host name for the ifxIFXHOST property.
- databaseName The name of the database from which the data source obtains connections. Example: Sample.
- ifxIFX_XASPEC Turn on this property when multiple users access the same database. Activating the property enforces tight coupling of XA transactions within the same global transaction ID, and requires the transactions to share lock space. These parameters help prevent transaction management errors from occurring in cases of multiple client requests. Turn on the ifxIFX_XASPEC property by assigning it the value of Y or y ; either character works because the setting is not case-specific. Turn the property off by assigning it the value of N or n. WebSphere Application Server ignores all other values. Your setting for the property overrides the Informix database system setting.
- informixLockModeWait Although not required, this property enables you to set the number of seconds that Informix software waits for a lock. By default, Informix code throws an exception if it cannot immediately acquire a lock. Example: 2.

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

Sybase

Sybase jConnect for JDBC driver
The Sybase jConnect JDBC driver is a Type 4 JDBC driver that provides JDBC access to the Sybase database. Sybase jConnect JDBC driver supports one phase data source:
```
com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource   
```
Requires JDBC driver files: jconn2.jar.
For IPv6 support: For
applications that access Sybase in an IPv6 environment, use the Sybase jConnect JDBC driver version 6.0 EBF 12884. This implementation uses different classes and therefore requires a different JAR file and a different implementation class designation. You can define the jConnect JDBC driver v6.0 EBF 12884 in the administrative console by selecting User-defined as the database type on the New JDBC provider page. On the JDBC provider general configuration page, replace the default JAR file name with jconn3.jar . For the implementation class, input com.sybase.jdbc3.jdbc.SybConnectionPoolDataSource . The data store helper class and required properties are the same for all Sybase JDBC drivers.Requires DataStoreHelper class:
```
com.ibm.websphere.rsadapter.SybaseDataStoreHelper
```
Requires a valid authentication alias. Requires properties:
- serverName The name of the database server. Example: myserver.mydomain.com .
- databaseName The name of the database from which the data source obtains connections. Example: Sample.
- portNumber The TCP/IP port number through which all communications to the server take place. Example: 4100.
- connectionProperties A custom property required for applications containing EJB 2.0 enterprise beans. Value: SELECT_OPENS_CURSOR=true(Type: java.lang.String)
Sybase jConnect JDBC driver (XA)
The Sybase jConnect JDBC driver (XA) is a Type 4 JDBC driver that provides XA-compliant JDBC access to the Sybase database.
Sybase jConnect JDBC driver (XA) supports two phase data source:
```
com.sybase.jdbc2.jdbc.SybXADataSource  
```
Requires JDBC driver files: jconn2.jar .
For IPv6 support: For applications that access Sybase in an IPv6 environment, use the Sybase jConnect JDBC driver version 6.0 EBF 12884. This implementation uses different classes and therefore requires a different JAR file and a different implementation class designation. You can define the jConnect JDBC driver v6.0 EBF 12884 in the administrative console by selecting User-defined as the database type on the New JDBC provider page. On the JDBC provider general configuration page, replace the default JAR file name with jconn3.jar . For the implementation class, input com.sybase.jdbc3.jdbc.SybXADataSource . The data store helper class and required properties are the same for all Sybase JDBC drivers. Requires DataStoreHelper class:
```
com.ibm.websphere.rsadapter.SybaseDataStoreHelper
```
Requires a valid authentication alias. Requires properties:
- serverName The name of the database server. Example: myserver.mydomain.com
- databaseName The name of the database from which the data source obtains connections. Example: Sample.
- portNumber The TCP/IP port number through which all communications to the server take place. Example: 4100.
- connectionProperties A custom property required for applications containing EJB 2.0 enterprise beans. Value: SELECT_OPENS_CURSOR=true(Type: java.lang.String)

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

Oracle

Oracle JDBC Driver
The Oracle JDBC Driver provides JDBC access to the Oracle database. This JDBC driver supports both Type 2 JDBC access and Type 4 JDBC access. Oracle JDBC Driver supports one phase data source:
```
 oracle.jdbc.pool.OracleConnectionPoolDataSource 
```
Requires JDBC driver files: ojdbc14.jar . (Note: If you require Oracle trace, use ojdbc14_g.jar .) Requires DataStoreHelper class:
```
com.ibm.websphere.rsadapter.OracleDataStoreHelper 
```
(Note: If you are running Oracle10g, use com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper .
Requires a valid authentication alias. Requires properties:
- URL The URL that indicates the database from which the data source obtains connections. Example: jdbc:oracle:thin:@myServer:1521:myDatabase , where myServer is the server name, 1521 is the port it is using for communication, and myDatabase is the database name.
Oracle JDBC Driver (XA)
The Oracle JDBC Driver (XA) provides XA-compliant JDBC access to the Oracle database. This JDBC driver supports both Type 2 JDBC access and Type 4 JDBC access. Oracle JDBC Driver (XA) supports two phase data source:
```
oracle.jdbc.xa.client.OracleXADataSource  
```
Requires JDBC driver files: ojdbc14.jar. (Note: If you require Oracle trace, use ojdbc14_g.jar .) Requires DataStoreHelper class:
```
com.ibm.websphere.rsadapter.OracleDataStoreHelper
```
(Note: If you are running Oracle10g, use com.ibm.websphere.rsadapter.Oracle10gDataStoreHelper .
Requires a valid authentication alias. Requires properties:
- URL The URL that indicates the database from which the data source obtains connections. Example: jdbc:oracle:thin:@myServer:1521:myDatabase , where myServer is the server name, 1521 is the port it is using for communication, and myDatabase is the database name.

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

MS SQL Server

DataDirect ConnectJDBC type 4 driver for MS SQL Server
DataDirect ConnectJDBC type 4 driver for MS SQL Server is a Type 4 JDBC driver that provides JDBC access to the MS SQL Server database. This provider is for use only with the Connect JDBC driver purchased from DataDirect Technologies. This JDBC provider supports this data source:
```
 com.ddtek.jdbcx.sqlserver.SQLServerDataSource  
```
Requires JDBC driver files:
```
sqlserver.jar  ,
base.jar  and util.jar
```
(The spy.jar file is optional. You need this file to enable spy logging. The spy.jar file is not in the same directory as the other three jar files. Instead, it is located in the ../spy/ directory.) Requires DataStoreHelper class:
```
com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper 
```
Requires a valid authentication alias. Requires properties:
- serverName The name of the server in which MS SQL Server resides. Example: myserver.mydomain.com
- portNumber The TCP/IP port that MS SQL Server uses for communication. Port 1433 is the default.
- databaseName The name of the database from which the data source obtains connections. Example: Sample.
DataDirect ConnectJDBC type 4 driver for MS SQL Server (XA)
DataDirect ConnectJDBC type 4 driver for MS SQL Server (XA) is a Type 4 JDBC driver which provides XA-compliant JDBC access to the MS SQL Server database. This provider is for use only with the Connect JDBC driver purchased from DataDirect Technologies.
This JDBC provider supports this data source:
```
com.ddtek.jdbcx.sqlserver.SQLServerDataSource.
 
```
Requires JDBC driver files:
```
sqlserver.jar  ,
base.jar  and util.jar.
```
(The spy.jar file is optional. You need this file to enable spy logging. The spy.jar file is not in the same directory as the other three jar files. Instead, it is located in the ../spy/ directory.) Requires DataStoreHelper class:
```
com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper 
```
Requires a valid authentication alias. Requires properties:
- serverName The name of the server in which MS SQL Server resides. Example: myserver.mydomain.com
- portNumber The TCP/IP port that MS SQL Server uses for communication. Port 1433 is the default.
- databaseName The name of the database from which the data source obtains connections. Example: Sample.
For more information on the DataDirect ConnectJDBC driver, visit the DataDirect Web site at: http://www.datadirect-technologies.com/
WebSphere embedded ConnectJDBC driver for MS SQL Server
WebSphere embedded ConnectJDBC driver for MS SQL Server is a Type 4 JDBC driver that provides JDBC access to the MS SQL Server database. This JDBC driver ships with WebSphere Application Server. Only use this provider with the Connect JDBC driver embedded in WebSphere; it cannot be used with a Connect JDBC driver purchased separately from DataDirect Technologies. This JDBC provider supports this data source:
```
com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource .
```
Requires JDBC driver files:
```
sqlserver.jar 
base.jar  and util.jar. 
```
(The spy.jar file is optional. You need this file to enable spy logging. The spy.jar file for the WebSphere embedded Connect JDBC driver ships with WebSphere Application Server. All the files are located in the WAS_HOME/lib/ directory.) Requires DataStoreHelper class:
```
com.ibm.websphere.rsadapter.WSConnectJDBCDataStoreHelper
```
Requires a valid authentication alias. Requires properties:
- serverName The name of the server in which MS SQL Server resides. Example: myserver.mydomain.com
- portNumber The TCP/IP port that MS SQL Server uses for communication. Port 1433 is the default.
- databaseName The name of the database from which the data source obtains connections. Example: Sample.
WebSphere embedded ConnectJDBC driver for MS SQL Server (XA)
WebSphere embedded ConnectJDBC driver for MS SQL Server (XA) is a Type 4 JDBC driver that provides JDBC access to the MS SQL Server database. This JDBC driver ships with WebSphere Application Server. Only use this provider with the Connect JDBC driver embedded in WebSphere; it cannot be used with 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. 
```
(An additional file, the spy.jar file, is optional. You need spy.jar for spy logging, which is a form of JDBC driver-level trace.
All of the JAR files in the previous list are shipped with WebSphere Application Server and are installed automatically with the product. They are also updated automatically when you apply WebSphere Application Server service packs. Requires DataStoreHelper class:
```
com.ibm.websphere.rsadapter.WSConnectJDBCDataStoreHelper 
```
Requires a valid authentication alias. Requires properties:
- serverName The name of the server in which MS SQL Server resides. Example: myserver.mydomain.com
- portNumber The TCP/IP port that MS SQL Server uses for communication. Port 1433 is the default.
- databaseName The name of the database from which the data source obtains connections. Example: Sample.
Patches to the IBM WebSphere Connect JDBC driver jar files are installed automatically when you apply WebSphere Application Server service packs. However, to update Microsoft SQL Server-side programs for this JDBC driver, go to the IBM FTP site for WebSphere Application Server embedded product updates. Use the following URL:
ftp://ftp.software.ibm.com/software/websphere/info/tools/DataDirect/datadirect.htm
An important server-side program is Stored Procedures for the Java Transaction API (JTA). Whether you need to run one or two phase transactions with the XA-enabled IBM WebSphere Connect JDBC driver, install Stored Procedures for JTA on all machines that run Microsoft SQL. The WebSphere Application Server installation disks contain a base level of Stored Procedures for JTA. Go to the previously listed FTP site for updates to this API. Install Stored Procedures for JTA by performing the following steps:
1. Determine whether you are running the 32-bit or 64-bit MS SQL Server and select the appropriate sqljbc.dll and instjdbc.sql files.
2. Stop your MS SQL Server service.
3. Copy the sqljdbc.dll file into your %SQL_SERVER_INSTALL%\Binn\ directory.
4. Restart the MS SQL Server service.
5. Run the instjdbc.sql script. (The script can be run by the MS SQL Server Query Analyzer or the ISQL utility).
```
ftp://ftp.software.ibm.com/software/websphere/info/tools/DataDirect/datadirect.htm 
```
DataDirect SequeLink type 3 JDBC driver for MS SQL Server -- Deprecated
This type 3 JDBC driver for MS SQL Server is deprecated in WebSphere Application Server Version 6.0. Therefore it is no longer an available choice among provider types in the administrative console.
For best results with WebSphere Application Server JDBC access to MS SQL Server, use only JDBC drivers that are not marked for deprecation. However, if continue using a deprecated driver for JDBC access to MS SQL Server, you can configure it through the WebSphere Application Server administrative console. Follow the steps listed in Configuring a JDBC provider using the administrative console. Be sure to select User-defined for the database type. This selection triggers the console to display default class files, data source interfaces, and so on for your user-defined JDBC provider type. Replace those defaults with the following settings that are specific to the DataDirect SequeLink type 3 JDBC driver. DataDirect SequeLink type 3 JDBC driver supports the following data source:
```
com.ddtek.jdbcx.sequelink.SequeLinkDataSource  
```
Requires JDBC driver files:
```
 sljc.jar   and  spy-sl.jar 
```
(The JDBC driver shipped with WebSphere Application Server requires the sljc.jar and the spy-sl.jar files. The JDBC driver purchased from DataDirect requires the sljc.jar and the spy.jar files. The spy.jar and spy-sl.jar files are optional. You need these files to enable spy logging.) Requires DataStoreHelper class:
```
com.ibm.websphere.rsadapter.SequeLinkDataStoreHelper
```
Requires a valid authentication alias. Requires properties:
- serverName The name of the server in which SequeLink Server resides. Example: myserver.mydomain.com
- portNumber The TCP/IP port that SequeLink Server uses for communication. By default, SequeLink Server uses port 19996.
- databaseName The name of the database from which the data source obtains connections. Example: Sample.
- enable2phase This property is necessary only if your application must participate in two-phase transactions. By default, Application Server sets a user-defined implementation type to a connection pool data source. The connection pool data source supports only one-phase transactions. Configure two-phase transaction support by setting the enable2Phase custom property on each data source that you create with your user-defined JDBC provider. Follow these steps:
  1. Go to the Custom properties administrative console page by clicking Resources > JDBC Providers > your_JDBC_provider > Data sources > your_data_source > Custom properties.
  2. Click New.
  3. Input enable2Phase as the property name and assign it the value of true. For Version 4 data sources, use a property that works in the opposite manner: Input disable2Phase and assign it the value of false .
The DataDirect SequeLink type 3 JDBC driver requires installation of SequeLink Server on all machines running MS SQL Server. See the readme.html file found in the DataDirect folder on the WebSphere Application Server CD for instructions on how to install SequeLink Server. (Install SequeLink Server from the WebSphere Application Server CD only if you are using the SequeLink JDBC driver embedded in WebSphere. Otherwise, install a copy of SequeLink Server purchased from DataDirect Technologies.) Patches to the IBM WebSphere SequeLink JDBC driver jar files are installed automatically when applying WebSphere Application Server service packs. If updates are ever needed for the Microsoft SQL Server-side installables (SequeLink server) for the IBM WebSphere SequeLink JDBC driver, they will be made available from the 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/
```
Microsoft JDBC driver for MS SQL Server 2000 -- Deprecated
This type 4 JDBC driver for MS SQL Server 2000 is deprecated in WebSphere Application Server Version 6.0. Therefore it is no longer an available choice among provider types in the administrative console.
For best results with WebSphere Application Server JDBC access to MS SQL Server, use only JDBC drivers that are not marked for deprecation. However, if continue using a deprecated driver for JDBC access to MS SQL Server, you can configure it through the WebSphere Application Server administrative console. Follow the steps listed in Configuring a JDBC provider using the administrative console. Be sure to select User-defined for the database type. This selection triggers the console to display default class files, data source interfaces, and so on for your user-defined JDBC provider type. Replace those defaults with the following settings that are specific to the Microsoft JDBC driver for MS SQL Server 2000. Microsoft JDBC driver for MS SQL Server 2000 supports the following data source:
```
com.microsoft.jdbcx.sqlserver.SQLServerDataSource  
```
Requires JDBC driver files:
```
mssqlserver.jar  ,
msbase.jar  and msutil.jar
```
(The spy.jar file is optional. You need it to enable spy logging. However, Microsoft does not ship the spy.jar file. Contact Microsoft about this issue.) Requires DataStoreHelper class:
```
com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper
```
Requires a valid authentication alias. Requires properties:
- serverName The name of the server in which MS SQL Server resides. Example: myserver.mydomain.com
- portNumber The TCP/IP port that MS SQL Server uses for communication. Port 1433 is the default.
- databaseName The name of the database from which the data source obtains connections. Example: Sample.
- enable2phase This property is necessary only if your application must participate in two-phase transactions. By default, Application Server sets a user-defined implementation type to a connection pool data source. The connection pool data source supports only one-phase transactions. Configure two-phase transaction support by setting the enable2Phase custom property on each data source that you create with your user-defined JDBC provider. Follow these steps:
  1. Go to the Custom properties administrative console page by clicking Resources > JDBC Providers > your_JDBC_provider > Data sources > your_data_source > Custom properties.
  2. Click New.
  3. Input enable2Phase as the property name and assign it the value of true. For Version 4 data sources, use a property that works in the opposite manner: Input disable2Phase and assign it the value of false .

For more information on the Microsoft JDBC driver for MS SQL Server 2000, visit the Microsoft Web site at:

http://www.microsoft.com/sql

Related concepts
Data sources
Resource adapter
JDBC providers