Re: configuration of c/s application -- MIDRANGE-L

Dan,

In a message dated 98-01-13 15:07:04 EST, you write:

> This is our project in a nutshell - Visual Basic-developed applications on
>  a Win 95/NT client, possibly downloaded from a file server, pointing to an
>  AS/400 via Client Access and TCP/IP and accessing databases via ODBC.  Our
>  group is now thinking about the network architecture and they are asking me
>  questions.  Some think we load Client Access on an NT file server and have
>  all clients "funnel" through that connection to the AS/400.  This can be
>  done, I'm sure, but I wonder if it is the most efficient method, especially
>  because users may number in the hundreds.  Should the VB application reside
>  on the PC instead, communicating directly with the AS/400?  If so, how best
>  to communicate with the AS/400 across the WAN?  Is it good to have Client
>  Access on dozens or hundreds of PCs talking to one AS/400?

Aaaaaaarrrrggghhh!  Assuming that you have the bandwidth (a big assumption,
since 90% of organizations of this size are underconfigured), you have other
issues unaddressed here.  How important is system availability?  If the
application resides on the client, does it have alternate routes to the data
available if the primary route is down (if not, the application might as well
reside on the server)?  How is CA licensing handled these days, per seat or
per AS/400 (sorry, not my job to keep up with this any more)?

We have several touch-screens running VB applications attached to the /400 via
NS/Router (which offers a site, rather than per-seat, license).  Connection is
via ESS/400 rather than ODBC, because the APPC connect is _MUCH_ faster.  Our
applications reside on the client because the primary server goes down
frequently, but there are routes around the server that cannot be accessed if
the application resides on the server.  Unless the /400 _is_ the server, I'd
recommend keeping everything that you can _off_ of the server...

>  My real question is, how do we size client server applications and how do
>  we best deploy them?  Where do we go for information on this subject?  I
>  realize that this is an open-ended question, but I must start somewhere.

Hmmmm.  There is material available from time to time, but it is usually
outdated before it's published.  Redbooks help, but they certainly aren't the
panacea that you seek.  As usual, "it depends".  When you live on the
"bleeding edge", you have to expect some blood to be spilled ;-).  Your _best_
resource will probably be in-house experimentation...

JMHO,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@aol.com

"I can't imagine why anyone would _need_ more than 640Kb of memory or 30Mb of
hard drive on a personal computer."  -- Bill Gates, author, "The Road Ahead"
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---