A typical JDBC Java application consists of a Java application
or applet, the JDBC Driver Manager, a vendor specific JDBC driver,
and a database. The JDBC Driver Manager is provided with the Java
SDK and its primary function is to load and register the vendor-specific JDBC
driver with the Java applications and then get out of the way. The
following diagram shows the various components of a client-server JDBC
application.
Figure 1-1 JDBC Client-Server Application
The HP Driver for JDBC is a vendor specific JDBC Driver that
allows Java applications to connect to ALLBASE/SQL or IMAGE/SQL databases
on MPE/iX or ALLBASE/SQL on HP-UX. The HP Driver for JDBC is a Type
3 (Network-Protocol) driver, meaning the driver translates the JDBC
API into a DBMS-independent protocol on the client-side, and then
translates to the ALLBASE/SQL protocol on the server. The driver
components on the client-side are written in 100% Pure Java, which
provides the complete compatibility with all Java Virtual Machines
on all platforms.
The document will only describe the specifics necessary to
use the HP Driver for JDBC, and not JDBC and JDBC drivers in general.
For a comprehensive discussion of JDBC, refer to:
JDBC Database Access with Java: A Tutorial and Annotated Reference, Graham
Hamilton, Rick Cattell, and Maydene Fisher, Addison-Wesley 1997.
