Yep, I agree. In our two tier aps using VB and the HP3000 we use Disc's
OmniAccess API which allows us to do just about anything on the 3k from the
client.
All of the Tier 3 Web Ap Servers I have looked at to date can begin using
ODBC/JDBC drivers "out of the box". And...most also seem to be able to
incorporate an API (OmniAccess, AIM, etc) with *some work* :)
There are definate advantages to the API approach in my mind.
Greg
> -----Original Message-----
> From: Thomas Dayton [SMTP:[log in to unmask]]
> Sent: Wednesday, June 16, 1999 1:13 PM
> Subject: Re: HP3000 Web Server
>
> Hi everyone,
>
> Greg describes an excellent multi-tier e-biz architecture which features
> our
> mutual buddy, the HP3000. However, I think its important to note that
> Tier #3
> (The App Server) does NOT need to necessarily use ODBC-like technology to
> perform the "application" part of the application server.
>
> We have seen several companies exploit their investment in HP3000 software
> (databases AND code) from the internet by "wrapping" their HP3000 business
> logic (COBOL, C, whatever) with light-weight middleware APIs which are
> called
> by the APP Server (Tier #3).
>
> The advantage of this architecture, IMHO, is the ability to re-use the
> incredible investment most folks have made in HP3000 applications -- not
> just
> Image databases. If you've already invested in COBOL/VPLUS/IMAGE, why the
> heck
> would you toss out the "application" layer and use only the database?
> I've yet
> to see an IMAGE database by itself serve as an application backbone.
> That's
> why most of us wrote code on top of the database.
>
> <plug>
>
> We've recently built a solution for a customer using Cold Fusion as the
> App
> Server which made calls to a standard "C" language DLL which implemented a
> series of RPCs to the HP3000. These RPCs (built with our
> middleware-generation
> product) represented a variety of "business functions" which were
> harvested
> from an existing COBOL/VPLUS/IMAGE application. All the investment in the
> COBOL, rules, and edits were preserved. This approach allowed our
> customer to
> leverage their IMAGE database PLUS the code they've written and maintained
> for
> years.
>
> The "C" language DLL was not hand-crafted. It was code-generated from an
> IDL-like specification which expressed each HP3000 transaction as a
> function
> name with discreet inputs and outputs. The scripting in Cold Fusion was
> simplicity itself.
>
> The end result was an industry-strength e-biz solution which re-used an
> application that had been strictly accessible from MPE sessions. Now,
> instead
> of hundreds of MPE logons, there is one session serving hundreds of
> internet
> users.
>
> </plug>
>
> If you're interested in pursuing this discussion further, I'd be happy to
> chat
> with you via voice or e-mail.
>
> Humbly,
> Thomas S. Dayton
> Premier Software Technologies, Inc.
> 530.268.1461
>
> > We are currently doing research into this very approach. In general, we
> are
> > heading towards a 3 to 4 tier approach:
> >
> > Tier 1: Browsers of the world
> >
> > Tier 2: Web Server running on NT/IIS (not likely) or Solaris (Apache,
> > Netscape Enterprise Server, etc).
> >
> > Tier 3: Web Application Server (Cold Fusion, NetDynamics, IBM
> WebSphere,
> > SilverStream, Haht, etc.)
> > NT or Solaris
> > Could be on the same box as tier 2
> > HP3000/Image connection via Disc, Minisoft or MBFoster
> ODBC
> > driver
> > Imsam Omnidex read/write access is a must for us
> > Web Ap Servers offer IDE, db connection pooling, session
> mgt,
> > clustering, debug, etc.
> >
> > Tier 4: Database Server: HP3000/Image
> >
> > We are focusing on Tier 3, the Web Application Server, selection. Tier
> 1 we
> > have no control over, Tier 4 is where we run our business, Tier 2 is a
> > fairly straight forward decision. Cold Fusion has the advantage of
> having a
> > shallow learning curve. NetDynamics is a high end product requiring
> Java
> > skills.
> >
> > I recommend going to the web sites of the Tier three vendors above and
> > reading their white papers. Also PC Week is due to have an evaluation
> of
> > Web Ap Servers in the near future.
> >
> > Greg Gibbons
> > See's Candies, Inc.
> > www.sees.com
> >
> > > -----Original Message-----
> > > From: Jeanne Pitts [SMTP:[log in to unmask]]
> > > Sent: Tuesday, June 15, 1999 3:34 PM
> > > Subject: HP3000 Web Server
> > >
> > > Hi,
> > >
> > > My company is interested in setting up an application that allows
> > > customer access for paying bills & history inquire on their accounts.
> > > Our current system is on an HP3000 using MPE, TurboImage and the
> > > application is written in COBOL. The HP3000 is accessible over an NT
> > > network and we do have an ISP plus with have HP terminals hooked up to
> > > the 3000. It's pretty primitive but functional. What products and
> steps
> > > do you recommend to get from where my company is now to where they
> want
> > > to go? We would like portability from the 3000 to the network & vise
> > > versa.
> > >
> > > Thanks in advance!
> > >
> > > Jeanne
> >
|
