HP Driver for JDBC User's Manual

Chapter 1 13

Introduction

HP JDBC Components

There are three components supplied with the HP JDBC product, the

JDBC Driver, the JDBC Monitor, and the JDBC Server. The user is

responsible for writing a Java application or applet that uses JDBC on

the client, as well as providing the ALLBASE/SQL or IMAGE/SQL

database on the server.

The HP Driver for JDBC is a set of Java classes that implement the

java.sql.* interfaces and provide an implementation of a JDBC

driver that can communicate with an ALLBASE/SQL or IMAGE/SQL

database. The HP Driver for JDBC typically will reside on the client

side of the user application. It provides the translation from the Java

language and the JDBC API to the HP proprietary network protocol.

The JDBC Monitor is a component that is installed on the JDBC

server host that manages all client JDBC Driver connections to the

server host. It is typically started as a daemon when the server

machine is booted. All JDBC client connections are made through the

JDBC Monitor. The monitor performs validation of the userid and

password that are passed in the client connection request and spawns

JDBC Server processes to serve each of the client connections. Once the

server process is spawned, the monitor returns to wait for the next

client connection.

The JDBC Server is the server process that is spawned by the JDBC

Monitor to service a client connection. It handles the translation from

the HP proprietary network protocol to the ALLBASE/SQL calls. There

is at least one JDBC Server process for each client connection to the

server host. More than one JDBC Server process may be used to handle

multiple client statements using the same connection. This component

also handles the translation from JDBC SQL to ALLBASE SQL and

conversion of the database data from ALLBASE/SQL format to JDBC

format.

Both the JDBC Monitor and the JDBC Server must be installed on the

same host where the ALLBASE/SQL or IMAGE/SQL databases reside.