NonStop Server for Java (NSJ) Programmer's Guide (NSJ 2.1+)

SQL/MP Driver Requirements
Before using the JDBC Driver for SQL/MP, the product components must be installed and the Java Virtual Machine (JVM)
must be compiled by the SQL Compiler. See the Softdoc or the README file that accompanies the NonStop Java product for
information about these tasks.
JDBC Driver Types
The following table describes the types of JDBC drivers:
Type
Written in
Java
Description
No. Name
1 JDBC-to-ODBC bridge Possibly Uses a JDBC-to-ODBC bridge to
translate JDBC calls to ODBC calls,
which are handled by an ODBC driver.
This requires an ODBC driver on the
client side and an ODBC server on the
server side.
2 Native protocol Partially Translates JDBC calls into the native
API for a particular database. The driver
must run on a machine where this to API
is available. (sqlmp and sqlmptx are
Type 2 drivers.)
3 Pure Java Entirely Translates JDBC calls to a
database-independent protocol for
transmission over the network. Server
middleware then translates this protocol
into a database's native protocol.
4 Native protocol,
Pure Java
Entirely Translates JDBC calls directly to the
network protocol of a particular
database. Thus, a JDBC program on the
client can call directly to the database
server.
Note: Compaq does not support third-party JDBC drivers, but any JDBC driver that is written entirely in Java
(that is, a Type 3 or a Type 4 driver) can run on top of NonStop Java. To use such a driver to connect your Java
program to a third-party database, see the third-party instructions for that driver.
JDBC DriverManager
The JDBC DriverManager maintains a list of available JDBC drivers. When a program calls the getConnection
method, the JDBC DriverManager searches this list and connects the calling program to the appropriate JDBC driver.