Re: [WEB400] Multiple web instances assistance and comments

["Nathan M. Andelin" <nandelin@xxxxxxxxxxxxxxxxxxx>]

> From: "Jeff Silberberg" <jsilberberg@mindspring.com>
> Then of course you have DNS, Firewall, and depending on Subnets,
> routing considerations for each IP/Instance...

Good point, Jeff.

> The biggest concern I would think will be user training...  If you
> do this the DNS portion of the URL Changes so now
> you will have:
> http://appl1.myhost.com
> http://app2.myhost.com
> http://app3.myhost.com

Another good point.

Rather than having different domain names names for different applications,
I believe another possibility is front-ending the AS/400 with an Intel
server (for example), running an IP sprayer software package, to reroute
http://myhost.com/app1 to the IP address pertaining to "app1" and so forth.

For temporarily disabling an application, Relational-Web also offers a nice
solution. No need to front-end the application/database server with an extra
Intel server. No need to purchase an IP sprayer software package. No need to
purchase or configure multiple IP addresses. No need to run multiple
instances of the HTTP server. No need to shut down the HTTP server. No
orphaned users, wondering why their requests are timing out with an HTTP
error message.

With Relational-Web, a system operator (or scheduled CL program) simply
invokes a command (ENDWEBAPP) to shutdown and temporarily disable any
individual application. While the application is temporarily unavailable,
any users would receive an HTML response, which might even indicate the
reason that the application is unavailable (ie. we're backing up some files
that are used by your program).  Although one application may be temporarily
unavailable, all others (as well as static pages), would be available.

Nathan M. Andelin
www.relational-data.com