Integrating JDBC Type 4 Driver With JBoss Applications

Starting the NonStop ODBC/MX Connectivity Service

The NonStop ODBC/MX Connectivity Service, also known as the MXCS Association Server, must be

installed and running on the NonStop system. Check the manual documentation (T7969G10) for

details on how to start the MXCS Association Server.

The following is a quick reference to start the MXCS Association Server from the TACL command

prompt as a super.super user:

<volume>.<subvolume>.mxoas /name $<process name>,

nowait, term $zhome/ -pn <port>

Example:

$data08.A2040209.mxoas /name $vn, nowait, term $zhome/ -pn 6100

Note: The above TACL command must be issued from an audited disk volume.

Starting the NonStop XABroker for global (XA) transactions

The NonStop XA Broker must be installed and running on the NonStop system. For more information

on how to start the XA Broker, see the XACI documentation (T0805H01).

TBD link to the XACI guide

Configuring JDBC Type 4 data source for the JBoss Application Server

The NonStopFiles_JBoss.zip also contains a file named sqlmx-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-ds.xml are:

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

<local-tx-datasource>

<jndi-name>SQLMXDS</jndi-name>

<connection-url>jdbc:t4sqlmx://16.1.1.1:6100/:</connection-url>

<driver-class>com.tandem.t4jdbc.SQLMXDriver</driver-class>

<user-name>username</user-name>

<password>password</password>

<connection-property name="schema">DUKESCHEMA

</connection-property>

<connection-property name="catalog">DUKECAT

</connection-property>

<connection-property name="T4LogLevel">ALL

</connection-property>

<connection-property name="T4LogFile">C:/T4.log

</connection-property>

<type-mapping>JDBC Type4</type-mapping>

</metadata>

<!—

Additional properties for the NonStop JDBC Type 4 driver

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

<connection-property

name="PROP_NAME">PROP_VALUE</connection>

-->

</local-tx-datasource>