At 12:24 PM 5/23/00, Dovid Samber wrote:
>    We are planning a web page for customers to access order status
>information and have become aware of the high resource consumption on the
>3000 when accessing Image data via ODBC.  An alternative of using Sockets
>and staying native mode on the 3000 has been proposed.
>    Any negatives in going the Sockets route?

Caution, this reply contains <PLUG>s.

ODBC calls CAN use a lot of CPU/Disc IO on the HP3000. With careful limits
placed on the SQL statements used in your web application, resource
consumption can be kept very small.

We have seen high utilization where keys are missing or not used
appropriately. For example using "less than" on an Image key is a serial
read. By enabling the dataset for BTREEs or TPI, an ODBC driver can use
additional relative operators.

Web Applications are easier to control than ad hoc tools (MS Access,
Crystal, etc.) because the SQL source is under IS control.

In answer to your question, yes there are some negatives to going
sockets.  Code needs to be written on both the HP3000 and your web server.
Detailed knowledge of writing socket applications is helpful. Portability
is hard to maintain.

There are also some positives.  Total control over how your data is
accessed. Reuse existing source code.

That is why...

<Here comes the PLUG parts, please feel free to ignore the rest of this note>

... MiniSoft <http://www.minisoft.com> provides a wide range of webbing
tools for the HP3000.

Short answers:

ODBC - As fast as the keys used. Need to know SQL.  Win32.

JDBC - As fast as the keys used. Need to know SQL. HP-UX, Solaris, Linux,
Win32.

MiddleMan (DA) - Intrinsic (Image, KSAM, MPE) calls. Win32.

MiddleMan (SA) - MiniSoft does security and socket calls for you. Win32.

Web Dimension - Your existing application and JDBC in a web page. HP-UX,
Solaris, Linux, Win32.

Javelin - Your existing application. Any web server.

Long answers:

- ODBC/32

If you limit the searches to key values only, permits quick and painless
access to Image/KSAM/MPE data. Minimal overhead (when used with keys).

Web application database links portable to other boxes (needed to satisfy
some bean counter but who would want to move the DB off the HP3000).

- JDBC

Same as ODBC with added benefit of host independence. Requires knowledge of
Java coding.

- MiddleMan (Data Access)

An ActiveX control callable with most PC tools. Use this where you have
extensive Image Intrinsic knowledge and the need for absolute control of
the calls being made. You can quickly replicate your business logic.

Limited to accessing the HP3000 but who wants to move to Unix
anyway.  Limits your Web Server to Win32 at this time.

- MiddleMan (Streams Access)

Wrappers for your sockets.  Our job handles password verification. Shipped
to the PC as an ActiveX component. Code needs to be created on the PC and
the HP3000.

Also limits your Web Server to Win32.

- Web Dimension

Mix existing applications and JDBC access from Java web server.  Define
where your want to pull data from and where it should go.  Mix and match
data sources and sinks.

Best if you know Java.

Javelin

Runs your existing applications from an applet in most browsers.

neal
800-682-0200