Data Direct Technologies SequeLink and Connect JDBC Drivers


Installation of Data Direct Technologies Products Shipped with WebSphere

Abstract

WebSphere 5.0 includes two JDBC drivers from Data Direct Technologies for enabling connectivity to Microsoft SQL Server. These drivers are the SequeLink and Connect JDBC drivers. Both JDBC drivers install automatically with WebSphere but may require additional setup on the machines where MS SQL Server instances are present. This document describes the additional setup required.

When installing WebSphere, the SequeLink and Connect JDBC driver jar files are placed automatically in the %WEBSPHERE_INSTALL%\AppServer\lib\ folder. The corresponding server-side installables for these drivers are available on CD #10.

SequeLink and Connect JDBC driver jar files
For the Connect driver
base.jar
spy.jar
sqlserver.jar
util.jar
For the SequeLink driver
sljc.jar
spy-sl53.jar

From time to time, patches are made available by Data Direct Technologies for the JDBC drivers and corresponding server installables. IBM maintains the following website for obtaining the most recent patches for the Data Direct Technologies products embedded in WebSphere,

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

Customers should check the above site for patches before opening any cases with WebSphere or Data Direct Technologies. It is also a good idea, when installing from scratch, to obtain the most recent versions from the above Data Direct driver update download page instead of from the WebSphere CD in order to have the latest fixes applied.

Quick Index

Server-side Installables Found on CD #10

WebSphere CD #10 contains the installable for the SequeLink Server required by the SequeLink JDBC driver and the "Stored Procedures for JTA" installation files required by the Connect JDBC driver. Installables on the CD must be installed manually as they do not automatically install with WebSphere.

Server-side Installables on CD #10

Stored Procedures for JTA installation files:

F:\ConnectJDBC-3.1\SQLServer JTA\instjdbc.sql
F:\ConnectJDBC-3.1\SQLServer JTA\sqljdbc.dll

How to install Stored Procedures for JTA

SequeLink Server Installable Files:

F:\SequeLink-5.3\Win\installs\SLsqlserverfix5.3\setup.exe

How to install SequeLink Server

How to install Stored Procedures for JTA

The Data Direct Technologies Connect JDBC driver requires installation of special stored procedures if using JTA (enable2Phase property set to true). For customers not wishing to enable two-phase commit, no additional installation is necessary for the Connect JDBC driver to function properly.

To install stored procedures for JTA, the following files are needed, available from CD #10,

F:\ConnectJDBC-3.1\SQLServer JTA\instjdbc.sql    
F:\ConnectJDBC-3.1\SQLServer JTA\sqljdbc.dll     

After locating the above files, perform the following steps,

Stop your MS SQL Server service. Drop the sqljdbc.dll file into your %SQL_SERVER_INSTALL%\Binn\ folder. Restart the MS SQL Server service and run the instjdbc.sql script. (The script can be run by the MS SQL Server Query Analyzer or the ISQL utility).

The first time the script is run, you may see errors related to removing stored procedures. This is expected since there are no existing procedures to uninstall when the script is run the first time.

Using the Connect JDBC driver in two-phase enabled mode also requires the Microsoft Distributed Transaction Coordinator service to be running on each machine where MS SQL Server is to be used. Additionally, the Stored Procedures for JTA must be installed on each MS SQL Server instance.

How to install SequeLink Server

As a type 3 JDBC driver, the SequeLink driver requires a SequeLink server to be installed and running on each machine running a MS SQL Server instance. The following steps describe how to install the SequeLink server,

  1. MDAC 2.6 SP1 is a prerequisite of SequeLink 5.3. Before installing SequeLink 5.3, you must install MDAC 2.6 SP1.
  2. Locate the SequeLink server installable files on CD #10.
  3. Run the following command,
    F:\SequeLink-5.3\Win\installs\SLsqlserverfix5.3\setup.exe /v"IPE=NO"   
    

The SequeLink server may be installed with or without a license key.

The /v"IPE=NO" argument installs the SequeLink server without a license key. When installed in this manner, the SequeLink server may be used only with the WebSphere embedded SequeLink JDBC driver.

Customers having purchased the SequeLink product from Data Direct Technologies will have a license key and should not use the /v"IPE=NO" argument when installing. They will be prompted during the installation to enter the license key. When installed with a license key, the SequeLink server may be used with both the WebSphere embedded SequeLink driver and the SequeLink driver as purchased from Data Direct Technologies.

The install will create SLAgent53 and SLSQLServer53 services. These services must be running on the machine where the MS SQL Server instance is installed to connect via the SequeLink JDBC driver.

Restrictions on Embedded Drivers

The Data Direct Technologies JDBC drivers embedded in WebSphere are licensed for use only within WebSphere, as WebSphere-managed DataSources. Included in the embedded drivers is a special locking mechanism to prevent these drivers from being used in a non-embedded manner. Customers should not attempt to use the Data Direct Technologies drivers embedded in WebSphere outside of the WebSphere product or for any other purposes.

Examples of non-embedded use include programmatically creating DataSource instances in an application or using the DriverManager to obtain a Connection. Applications attempting to access the embedded drivers in this unsupported manner will fail with license errors.

Customers with business requirements to use the drivers outside of WebSphere may purchase the drivers from Data Direct Technologies.

Related Links

Technical support

Customers with service agreements may call IBM WebSphere support with questions regarding SequeLink and Connect JDBC drivers embedded in WebSphere. (1-800-IBM-SERV for US calls only)