Multiple Web Sites on one A5 WAS

[Steve Workings]

Re: Multiple Web Sites on one A5 WAS

How to run multiple applications or web sites by using multiple Application Server configuration files

Traditionally, Application Server administrators provide service for multiple applications by using a single instance of the Application Server, placing each distinct application within a different subfolder under the document root. While this is quite effective, it results in cluttered URLs, such as http://www.server.com/application1 and http://www.server.com/application2, and shares sessions between sites. By using multiple instances of the Application Server, each to provide service for only one specific application or site, sessions are no longer shared and URLs may be further customized. This configuration requires 1 IP address per application or site.

1. Make sure that the server's operating system has at least one IP address for each application you would like to provide service for. For specific information on how to do this, consult your network administrator.
2. Configure DNS for www.application1.com to point to IP address 1 and www.application2.com to point to IP address 2. For specific information on how to do this, consult your network administrator.
3. Create an XML configuration file for each application and start server instances for each site (see above). Any errors about the servers being unable to start at this point are expected.
4. Configure the server for application 1 to use the assigned IP address (on the Advanced tab). Also change the document root and any other settings as required. Repeat for application 2.
5. Click Start to start each instance of the Application Server.

[Clipper87]

Re: Multiple Web Sites on one A5 WAS

So, before I run down this path and join the fray:

I have VPS running Windows Server 2008 R2 with IIS v7.5. It seems I should be able to configure IIS to detect multiple domains and point different domain traffic to different ports (e.g., 81, 82, 83 ...). Then I'd run multiple AFWS' listening on different ports. e.g. site1 is redirected to AFWS running on port 81 (AFWS:81), site2 is redirected to AFWS:82, site2 is redirected to AFWS:83, etc.

Should this work?

Lee,

Yes that will work. I've done such a setup. Note however you'll still need one instance of the WAS per domain because as Steve Wood points out (see his posting earlier in this thread) "The fact is you can tell Apache what the DocumentRoot is, but I can find no way for Apache to tell ALPHA what the DocumentRoot is."
Apache or IIS7 doesn't make a difference here.

Your approach is cheaper then having an IP address per domain if at all you can buy IP addresses that easy. Out here every request needs proper justification or you don't get it. The pool of IPV4 addresses is running dry, Microsoft just bought bankrupt Nortel's IPV4 addresses for 7,5 m$.

Cheers