|
Problem(Abstract) |
When using JDBC™ distributed transaction through Java™
Transaction API (JTA) with WebSphere® embedded Connect JDBC driver to
access a Microsoft® SQL Server database, a set of stored procedures must
be installed on the Microsoft SQL Server installation.
This technote explains the procedure to install the required Microsoft SQL
Server JDBC XA procedures. |
|
|
|
Resolving the
problem |
- Download the ConnectJDBC33-JTA.zip for WebSphere embedded connect JDBC
3.3. driver from DataDirect
Connect JDBC and SequeLink JDBC Drivers.
- Unzip the file ConnectJDBC33-JTA.zip into a temporary directory, such
as temp_dir.
- Copy the sqljdbc.dll file, either the 32-bit or 64-bit version, to the
Microsoft SQL Server database server:
- On a 32-bit platform, copy the sqljdbc.dll file from the
temp_dir/SQLServer JTA/32Bit directory to the
SQL_Server_Root/binn directory of the Microsoft SQL Server database
server.
- On a 64-bit platform, copy the sqljdbc.dll from the
temp_dir/SQLServer JTA/64Bit directory to the
SQL_Server_Root/binn directory of the Microsoft SQL Server database
server where:
SQL_Server_Root is your Microsoft SQL Server installation
directory.
From the database server, use the ISQL utility to run the
instjdbc.sql script. As a precaution, the system administrator
should back up the master database before running instjdbc.sql.
At a command prompt, run instjdbc.sql using the following syntax:
ISQL -Usa
-Psa_password -Sserver_name -ilocation\instjdbc.sql
where:
sa_password is the password of the system administrator.
server_name is the name of the server on which the Microsoft SQL
Server database resides.
location is the full path to instjdbc.sql. This script is located
in the temp_dir/SQLServer JTA directory.
The instjdbc.sql script generates many messages. In general, these
messages can be ignored; however, the system administrator should scan the
output for any messages that indicate an execution error.
The last message should indicate that instjdbc.sql ran successfully. The
script fails when there is insufficient space available in the master
database to store the JDBC XA procedures or to log changes to existing
procedures.
For more information, refer to DataDirect Connect for JDBC User's Guide
and Reference which is available at DataDirect's
JDBC Product Documentation. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|