JDBC Type 2 Driver Programmer's Reference for SQL/MX Release 3.2.1 (H06.26+, J06.15+)

1 Introduction to JDBC/MX Driver
The HP JDBC/MX Driver 3.2 for NonStop SQL/MX implements the JDBC technology that conforms
to the standard JDBC 3.0 Data Access API. This JDBC/MX driver enables Java applications to use
HP NonStop SQL/MX to access NonStop SQL databases.
For more information on the JDBC APIs associated with the JDBC/MX implementation, see “Oracle
documents” (page 10). 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).
The JDBC/MX driver together with HP NonStop Server for Java 5 is a Java environment that supports
compact, concurrent, dynamic, portable programs for the enterprise server. The JDBC/MX driver
requires NonStop Server for Java 5 and SQL/MX, which both require the HP NonStop Open
System Services (OSS) environment. The NonStop Server for Java 5 uses the HP NonStop operating
system to add the NonStop system fundamentals of scalability and program persistence to the Java
environment.
This section explains these subjects:
• “JDBC/MX Architecture” (page 15)
• “JDBC API Packages” (page 16)
• “Sample Programs Summary” (page 16)
JDBC/MX Architecture
The JDBC/MX driver is a Type 2 driver; it employs proprietary native APIs to use SQL/MX to access
NonStop SQL databases. The native API of SQL/MX cannot be called from client systems. For this
reason, the JDBC/MX driver runs on NonStop servers only.
The JDBC/MX driver is best suited for a three-tier model. In the three-tier model, commands are
sent to a middle tier of services, which then sends the commands to the data source. The data
source processes the commands and sends the results back to the middle tier, which then sends
them to the user. The middle tier makes it possible to maintain control over access and the kinds
of updates that can be made to corporate data. Another advantage is that it simplifies the
deployment of applications. Finally, in many cases, the three-tier architecture can provide
performance advantages.
The following figure illustrates a three-tier architecture for database access:
Figure 1 Architecture of the JDBC/MX Driver
JDBC/MX Architecture 15