1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- ======================================================================-->
<!-- New ConnectionManager setup for jTDS Sybase/Mcrosoft SQL Server driver-->
<!-- You may download the latest jTDS driver from *SourceForge* -->
<!-- http://jtds.sourceforge.net -->
<!-- ===================================================================== -->
<datasources>
<xa-datasource>
<jndi-name>MSSQLXADS</jndi-name>
<track-connection-by-tx/>
<isSameRM-override-value>false</isSameRM-override-value>
<xa-datasource-class>net.sourceforge.jtds.jdbcx.JtdsDataSource</xa-datasource-class>
<xa-datasource-property name="ServerName">localhost</xa-datasource-property>
<xa-datasource-property name="DatabaseName">xxxx</xa-datasource-property>
<xa-datasource-property name="Tds">8.0</xa-datasource-property>
<!--
You are recommended to use prepareSql=2 with true distributed transactions.
If a temp stored procedure is created and then the container rolls back the
transaction, the driver's procedure cache will be out of line with the server.
-->
<xa-datasource-property name="PrepareSql">2</xa-datasource-property>
<!--
Set this property to true to cause the driver to emulate distributed transactions.
False option only works for SQL Server 2000 with MSDTC and JtdsXA.DLL installed.
-->
<xa-datasource-property name="XaEmulation">false</xa-datasource-property>
<!--
Use this property to enable logging but NB: jTDS produces lots of output!
<xa-datasource-property name="LogFile">c:/temp/log.txt</xa-datasource-property>
-->
<valid-connection-sql>SELECT 1</valid-connection-sql>
<user-name>someone</user-name>
<password>secret</password>
</xa-datasource>
</datasources>
|
