Re: CGIDEV2 question

othe way is

1.- purchase two (or more) public IP address,

2.- in the intranet firewall configure NAT protocol
for redirecting each public IP to the same internal IP (the iSeries IP)
but to different ports

i.e.
121.121.121.121 goes to 192.168.1.1 port 1492
121.121.121.122 goes to 192.168.1.1 port 1493

this way you've separated apache config files, one for each port, and the
best is you can off one instance but the other is running, using virtual
servers (several servers in the same port) this can be a problem.

anyway virtual servers works fine, We've using even mix of the two cases in
the same iSeries (port 80 serving four applications with different folders
and two different ports attached to two public IP) all the client using port
80 because some clients can't run other port than 80 in the browsers.



--
Saludos/Regards,
Guillermo Andrades
CPI Software
http://www.CpiS.es
http://www.RpgForWeb.com




On 3/23/06, Tom Jedrzejewicz <tomjedrz@xxxxxxxxx> wrote:
>
> On 3/22/06, web400@xxxxxxxxxxxxxxxx <web400@xxxxxxxxxxxxxxxx> wrote:
>
> > True, but in that case you're using a separate IP address for each
> domain
> > name instead of a different port. That should work with different
> > instances too. Just have each instance bind to a different IP address.
> ...
> > But, what didn't occur to me in that last message, is that you could
> > potentially run different instances under different IP addresses instead
> > of different port numbers.  That would work.
>
> This is a great idea, and I like it far better than using different
> ports.  Put a second IP address on iSeries, and have the test/dev
> instance listen on that IP and the production instance listen on the
> original (primary) IP.  I wish I had thought about it when I first
> setup CGIDEV2 on my iSeries.
>
> --
> Tom Jedrzejewicz
> tomjedrz@xxxxxxxxx
>
> --
> This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> To post a message email: WEB400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/web400.
>
>