Re: Massive IP address change.

[Jim Oberholtzer <midrangel@xxxxxxxxxx>]

Rob,

True, however you can easily set up virtual hosts in Apache, and maybe 
more beneficial to you, alias names.  The documentation on how to do 
these on the internet is actually pretty good, even I was able to figure 
it out.

From a performance perspective, as long as all the HTTP instances are 
running in the same memory it does not matter if there are multiple 
instance of Apache or not, the exception to that is if the Zend Server 
is part of the mix.  If the Zend server is there then you really should 
have one instance of Apache that starts the Zend Server and put virtual 
hosts on that instance.  MySQL same thing, really only one daemon should 
be running.

You can play with the Apache directives on your PC and get them working 
there before you push them up to the IBM i instance.  Nearly all the 
directives are the same, the ones your interested in now anyway.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 4/26/2011 7:11 AM, rob@xxxxxxxxx wrote:
> Vern,
>
> It was rather tangential, true.  And your points are valid.  And I really
> am raw in this area.  I just think the average user doesn't like URLs like
> http://something:83
>
>
> Rob Berendt
> -- Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 
> Ship to: Dock 108 6928N 400E Kendallville, IN 46755 
> http://www.dekko.com From: Vern Hamberg <vhamberg@xxxxxxxxxxx> To: 
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> Date: 
> 04/26/2011 08:02 AM Subject: Re: Massive IP address change. Sent by: 
> midrange-l-bounces@xxxxxxxxxxxx Rob I'm not sure how this is a 
> response to what I said. Nonetheless, there are advantages to multiple 
> server instances. Simplicity is one of these. Maybe this can be 
> compared to the simplicity in the single modules of modular 
> programming, but some might consider that a stretch. The other is 
> administration - if all of your apps are configured in one file, with 
> multiple "listen" directives and virtual hosts or redirects, then when 
> you shut it down, you shut down everything. With multiple server 
> instances, if there is a problem with one, it does not have to affect 
> everyone else. So there's no right or wrong here - Apache has so many 
> options, so many ways to do things - you'd almost think it is Perl! 
> TMTOWTDI - There's more than one way to do it! Vern On 4/26/2011 6:10 
> AM, rob@xxxxxxxxx wrote:
> > >  While it may be possible for a good person to get by with one apache
> > >  config file and coding for all the variety of things they may be running
> > >  you often find that "vendor a" wants his own config file and their
> support
> > >  will look upon a shared config file with about as much disdain as an ERP
> > >  vendor will with a modified order entry program.
> > >
> > >
> > >  Rob Berendt
> > >  -- Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738
> > >  Ship to: Dock 108 6928N 400E Kendallville, IN 46755