Integrating JDBC Type 4 Driver With JBoss Applications

</datasources>

Configuring JDBC Type 4 XA data source for the JBoss Application Server

The NonStopFiles_JBoss.zip also contains a file named sqlmx-xa-ds.xml. This file contains the

configuration to create the default data source needed by the Duke’s Bank sample to communicate

with the NonStop SQL/MX Database.

The contents of the sqlmx-xa-ds.xml are:

<?xml version="1.0" encoding="UTF-8"?>

<xa-datasource>

<jndi-name>SQLMXXA</jndi-name>

<track-connection-by-tx>true</track-connection-by-tx>

<xa-datasource-property

name="Url">jdbc:t4sqlmx://16.1.1.1:19850/:

</xa-datasource-property>

<isSameRM-override-value>false</isSameRM-override-value>

<xa-datasource-class>com.tandem.t4jdbc.SQLMXXADataSource

</xa-datasource-class>

<xa-datasource-property name="User">username

</xa-datasource-property>

<xa-datasource-property name="Password">password

</xa-datasource-property>

<xa-datasource-property name="Schema">XASCHEMA

</xa-datasource-property>

<xa-datasource-property name="Catalog">XACAT

</xa-datasource-property>

<xa-datasource-property name="ServerDataSource">XADS

</xa-datasource-property>

<!—

Additional properties for the NonaStop JDBC Type 4 driver

can be set here by adding additional tags of the type:

<xa-datasource-property name="PROP_NAME">PROP_VALUE</xa-

datasource-property> -->

</xa-datasource>

</datasources>

Edit the value of the <xa-datasource-property name="Url"> for XA Transactions and <connection-url>

element for Non-XA Transactions respectively for the location where the MXCS Association Server is

running.

Also, edit the values of the <user-name> and <password> elements to reflect a valid user on the

NonStop system that has sufficient privileges to access the Duke’s Bank sample database.

You can add additional Type 4 Driver specific properties by using the <connection-property> tag.

Refer to the Type 4 Driver manual for a list of valid properties and their effects.

Place the sqlmx-xa-ds.xml file in the JBOSS_HOME/server/default/deploy directory.

Also, from the same directory (JBOSS_HOME/server/default/deploy), remove the existing hsqldb-

ds.xml file. This will prevent the duplicate definition of the Java Naming and Directory Interface (JNDI)

named “DefaultDS” during the server startup process.