JDBC Type 4 Driver Programmer's Reference for SQL/MX Release 3.2.1

1 Introduction to HP NonStop JDBC Type 4 Driver
• “Type 4 Driver API Package” (page 14)
• “Type 4 Driver Architecture” (page 14)
“Client Platforms Supported” (page 14)◦
◦ “Accessing a Database with the Type 4 Driver” (page 14)
• “Samples” (page 15)
Type 4 Driver API Package
The Type 4 driver package, com.tandem.t4jdbc, is shipped with the driver software. For class
and method descriptions, see the HP NonStop JDBC Type 4 Driver API Reference manual in the
NonStop Technical Library at Business Solution Center (BSC).
The NonStop JDBC Type 4 Driver (here after Type 4 driver) implements JDBC technology that
conforms to the standard JDBC 3.0 Data Access API. This driver enables Java applications to use
HP NonStop SQL/MX Release 3.0 or later versions to access NonStop SQL databases.
To obtain detailed information on the standard JDBC API, you should download the JDBC API
documentation provided by Oracle (http://www.oracle.com/technetwork/java/
download-141179.html).
Type 4 Driver Architecture
• “Client Platforms Supported” (page 14)
• “Accessing a Database with the Type 4 Driver” (page 14)
The Type 4 driver uses JDBC 3.0 standard functionality to allow Java clients access to NonStop
SQL/MX from client platforms.
The Type 4 driver requires these products on the NonStop server: the HP NonStop SQL Connectivity
Service (MXCS) and NonStop SQL/MX Release 3.0 or later versions, which both require the HP
NonStop Open System Services (OSS) environment.
The SQL/MX Connectivity Service (MXCS) must be running on the NonStop system. For more
information, see the HP NonStop Connectivity Service Manual for SQL/MX Release 3.2.1.
For XA transactions, the Type 4 driver requires the HP NonStop XA Broker product installed on the
NonStop server.
Client Platforms Supported
Java enabled platforms that support JDK 1.5 or later. For more information, see the softdoc file
delivered with the product.
Accessing a Database with the Type 4 Driver
1. A Java client application establishes a connection.
2. The Type 4 driver accesses an MXCS association server on the NonStop system.
3. The association server returns a handle for an MXCS server process to the Type 4 driver.
4. The driver makes a connection with the MXCS server process and returns that connection to
the client.
5. The MXCS process receives JDBC Type 4 driver requests from the client and processes them
using the SQL/MX database engine.
The following figure illustrates database access using the Type 4 driver:
14 Introduction to HP NonStop JDBC Type 4 Driver