Great, thanks so much for everyone's help. I will give that a go and see what happens.
/b;
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Mark Murphy/STAR BASE Consulting Inc.
Sent: Thursday, February 17, 2011 4:56 PM
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] Multiple Sites on Zend Server
If you look at the way Apache arranges things in it's conf files you will find that the main httpd.conf contains a bunch of includes that you can comment in (remove the comment sign) to implement. One of those is vhosts. The vhost.conf looks a lot like the below without all the individual vhosts. It just gives you a shell with the NameVirtualHost tag. In that file I like to add another include that looks something like:
Include vhosts\*.conf
Then I create a new directory named vhosts in which I put a conf file for each vhost that I want to configure. This has some advantages over just keeping the configuration in the main httpd.conf, or in the vhosts.conf files.
The main advantage is that when I want to modify a vhost, I just go to the vhost directory, and modify the appropriate file which I name the same as the server name with a .conf extension. I then only have access to a single config, and just that one is modified. If you keep your server config under source control, this will allow you to config and manage a single host at a time.
To add a new host, all I have to do is copy one that is close, and make a couple modifications. Cycle the server and the new host is there.
One thing you need to do to make all this work is have the virtual host's address resolved in your hosts file, or a DNS that is accessible to the Apache server.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
-----web400-bounces@xxxxxxxxxxxx wrote: -----
To: Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
From: Kevin Schroeder
Sent by: web400-bounces@xxxxxxxxxxxx
Date: 02/17/2011 04:10PM
Subject: Re: [WEB400] Multiple Sites on Zend Server
You don't even need to do that
NameVirtualHost *:80
<VirtualHost *:80>
ServerName pc.simcoeparts.com
DocumentRoot /www/zendsvr/htdocs/PC
</VirtualHost>
<VirtualHost *:80>
ServerName isd.simcoeparts.com
DocumentRoot /www/zendsvr/htdocs/ISD
</VirtualHost>
<VirtualHost *:80>
ServerName hr.simcoeparts.com
DocumentRoot /www/zendsvr/htdocs/HR
</VirtualHost>
Kevin Schroeder
Technology Evangelist
Zend Technologies, Ltd.
www.zend.com
www.twitter.com/kpschrade
www.eschrade.com
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Dayberry, Joshua
Sent: Thursday, February 17, 2011 3:00 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Multiple Sites on Zend Server
I am not all that familiar with IIS, but I believe what you are looking
for in apache is called a VirtualHost. You can segment by IP or
hostname (as long as your aren't using SSL) and each can have its own
document root.
If each hostname had a different IP, this would be the basic pattern.
Check out this documentation for a better explanation.
http://httpd.apache.org/docs/2.2/vhosts/
pc.simcoeparts.com->10.0.0.1
isd.simcoepart.com->10.0.0.2
hr.simcoeparts.com->10.0.0.3
<VirtualHost 10.0.0.1:80>
DocumentRoot /www/zendsvr/htdocs/PC
</VirtualHost>
<VirtualHost 10.0.0.2:80>
DocumentRoot /www/zendsvr/htdocs/ISD
</VirtualHost>
<VirtualHost 10.0.0.3:80>
DocumentRoot /www/zendsvr/htdocs/HR
</VirtualHost>
Joshua Dayberry
Senior Web Developer / Information Services
UnitedHealthOne
Golden Rule Insurance Company
7440 Woodland Drive
Indianapolis, IN 46278
Phone: 317.715.7541
E-mail: jdayberry@xxxxxxxxxxxxxx
"Everything should be made as simple as possible, but not simpler."
Albert Einstein
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Brian Piotrowski
Sent: Thursday, February 17, 2011 3:39 PM
To: Web Enabling the AS400 / iSeries
Subject: [WEB400] Multiple Sites on Zend Server
Hi All,
I have a question with regards to running multiple sites off the server.
My ultimate goal is to move all of our internal websites off our (gasp!)
Microsoft Windows 2003 server and onto the 400.
However, I'm not sure how to handle multiple websites. For example, on
our IIS, we have these sites:
pc.simcoeparts.com
isd.simcoepart.com
hr.simcoeparts.com
etc..
All are controlled by a host header file (PC, ISD, HR), which we then
map back to the web server via a DNS host entry. I know I need to
change the DNS entry to point from the MS Web server to the AS400
address, but I am unsure on how to set up the header file for multiple
sites. Further to that, can I assume that each of the website files
would be contained in their own separate folders (ie:
/www/zendsvr/htdocs/PC, /www/zendsvr/htdocs/ISD, etc.)?
Thanks!
/b;
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Assistant Mgr. - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x343
Fx: 705-435-5029
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
http://www.simcoeparts.com
Please consider the environment. Don't print this e-mail unless you
really need to.
The information contained in this communication is confidential and
intended only for the use of those to whom it is addressed. If you have
received this communication in error, please notify me by telephone
(collect if necessary) and delete or destroy any copies of it. Thank
you!
midrange.com
