Web Enabling Your HP 3000

Appendix: Third Party Middleware and Tools
ADBC (Adager DataBase Connectivity)
ADBC Technology requires a Java client (using native methods) to communicate as directly as
possible with the IMAGE intrinsics. A “monitor” program on the HP e3000 may be required, but,
ideally, there should be a minimum of layers between the client and the IMAGE intrinsics.
ADBC is a registered trademark of Adager Corporation.
ADBC/API, an implementation of ADBC technology developed by Advanced Network Systems,
Inc. consists of a set of Java objects that allow developers to write Java applications, web-
enable applications, and implement e-commerce solutions that access data on an HP e3000
using any Java-enabled client or Java server application (under MPE/iX, Windows, Mac OS,
Linux, Unix, and so on). The API provides you access to your IMAGE databases without using
ODBC or JDBC, as well as access to your KSAM, MPE, and SPOOL files. It also has objects that
pass queries to the LISTSPF, and SPOOL commands to pass the results back to your ADBC
objects.
All ADBC/API objects communicate directly with the native intrinsics on the HP e3000 for
optimum performance. ADBC API is very user friendly, and allows any developer to write Java
applications that access your HP e3000 without any HP e3000 knowledge. The API is object-
oriented to expedite application development. ADBC /API can be used with all the popular IDE
developer tools such as Visual Café and J++. You can also use any editor to write server-side
Java (servlets).
ADBC/API comes with a set of Java objects (erp3000) that gives you complete object oriented
interfaces to ManMan and MM3000 applications. Any application, from any platform, can be
easily integrated into ManMan and MM3000 using standards such as CORBA, Java Messaging,
and Java RMI. Using the ADBC/API, HP e3000 driver and a Java programmer you can read/write
IMAGE, MPE, KSAM, Spool files from your HP e3000, from any web-enabled Java-enabled
application.
Real-life applications
ADBC /API is currently in use by applications in the manufacturing and medical research sec-
tors. In one case, an ADBC customer (and Java developer) used ADBC and erp3000 to interface
a virtual shop-floor control solution to ManMan and MM3000, opening access of this developer’s
product to the HP e3000. This Java developer, in a week’s time, interfaced his application to
ManMan using ABDC and erp3000 without any knowledge of the HP e3000 specifics. The
Javadoc (documentation) he created from the Java API gave the developer all the information
he needed to use the erp3000 interface, without the need to place any ADBC support calls.
Other customers have used ADBC to web-enable Medical Research applications, interfaces to
SAP/R3, mission-critical sales orders, Quote Systems that extract data from IMAGE databases to
print, fax or email formal quotes, purchase order inquiry systems, etc.
Additional information on ADBC contact Advanced Network Systems, Inc.
(http://www.advnetsys.com) or Adager Corporation (http://www.adager.com).
20