Web Enabling Your HP 3000

7
The following diagram shows a three-tier architecture of a Web-Database ODBC model, Web
browser, Web server, and database server. The Web browser is on any PC or workstation client.
The Web server includes an HTTP server and a Web GUI tools application running on NT. The
database server has ALLBASE/SQL or IMAGE/SQL running on the HP e3000. When a Web
browser requests a data page from the Web server, the Web server uses an application program
to access databases via an ODBC driver, generates an HTML-data page on-the-fly, then passes
the page to the Web browser. The integration of database occurs between the Web server and
database server, and is transparent to the browser.
JDBC
Java Database Connectivity (JDBC) is the industry standard open interface API for database
access using Java. It allows Java programmers to issue SQL statements and process the results.
JDBC can be divided into four components:
• JDBC Driver Manger.
• JDBC Driver Interfaces.
• JDBC Exception Classes.
• Vendor specific JDBC Driver.
The first three components are included as part of JavaSoft JDBC package. The fourth part,
the JDBC Driver, is obtained separately from the driver vendors. With the JDBC API, JDBC
applications call the JDBC Driver Manager to bind JDBC driver. The JDBC driver then establish-
es a network connection with a database server, sends SQL statements, and processes the
results.
HP has selected the network-protocol, all-Java driver type for the JDBC driver implementation.
It is a thin-client implementation written in pure Java. HP JDBC driver executes on the client
machine and is best suited for Internet/ intranet-based concurrent data access applications. The
HP JDBC driver allows Java applications to access data stored in IMAGE/SQL and
ALLBASE/SQL on the HP e3000. The HP JDBC driver is bundled in MPE/iX 6.0 Express 1.
ODBC
Driver
Server
Web
GUI
App.
ODBC
Driver
Client
Web
Server
IMAGE/SQL
ALLBASE/SQL
Web
Browser
Intranet/
Internet
HP e3000
NT
Three-tier Web-Database ODBC Architecture