|
Home > Archive > IIS Server > June 2005 > How to set up multiple IIS 6.0 Servers Hosting the same .Net app
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
How to set up multiple IIS 6.0 Servers Hosting the same .Net app
|
|
| Lost With IIS 2005-06-24, 8:48 pm |
| I have a relatively simple but (seemingly common) dilemma. Here is my
situation:
I have a ASP.Net/VB.Net intranet application going against SQL Server which
works great on a single IIS Server. It is a pretty straightfoward OLTP
application with a database backend and also stores images/PDFs on the server.
I want to configure another IIS server to serve up the same content but I
don't want to have to roll out code to both servers everytime I make update.
Also, since the images/PDFs are stored on the original server, I want to be
able to access them using the second server as well (without duplicating
them).
1. How do I configure the second IIS 6.0 server so that I do not have to
roll out code to both whenever I make updates? I tried having the URL point
to a share on the original IIS Server but I'm running into a slew of
problems. Could not get the site up.
2. How do I create a share to store the images/PDFs so that both sites can
access those items? I am running in a Workgroup so the ASP.Net account is
specific to each machine.
This seems like a pretty common requirement but I am lost.
Thanks!
| |
| Trent Jones 2005-06-24, 8:48 pm |
|
"Lost With IIS" <Lost With IIS@discussions.microsoft.com> wrote in message
news:F52DE1EC-CD96-4C50-B156-8380641F6AAF@microsoft.com...
>I have a relatively simple but (seemingly common) dilemma. Here is my
> situation:
>
> I have a ASP.Net/VB.Net intranet application going against SQL Server
> which
> works great on a single IIS Server. It is a pretty straightfoward OLTP
> application with a database backend and also stores images/PDFs on the
> server.
>
> I want to configure another IIS server to serve up the same content but I
> don't want to have to roll out code to both servers everytime I make
> update.
> Also, since the images/PDFs are stored on the original server, I want to
> be
> able to access them using the second server as well (without duplicating
> them).
What's the purpose of this? How you set it up depends on whether you are
doing this for load balancing, fault tolerance, just for the heck of it,
etc.
The simplest way to do it is on the "Home Directory" tab on the IIS site
properties you could select content to come from a share on another computer
and point it to the existing server's site home directory.
- SG
| |
| Jeff Cochran 2005-06-26, 2:47 am |
| On Fri, 24 Jun 2005 16:42:02 -0700, "Lost With IIS" <Lost With
IIS@discussions.microsoft.com> wrote:
>I have a relatively simple but (seemingly common) dilemma. Here is my
>situation:
>
>I have a ASP.Net/VB.Net intranet application going against SQL Server which
>works great on a single IIS Server. It is a pretty straightfoward OLTP
>application with a database backend and also stores images/PDFs on the server.
>
>I want to configure another IIS server to serve up the same content but I
>don't want to have to roll out code to both servers everytime I make update.
>Also, since the images/PDFs are stored on the original server, I want to be
>able to access them using the second server as well (without duplicating
>them).
>
>1. How do I configure the second IIS 6.0 server so that I do not have to
>roll out code to both whenever I make updates? I tried having the URL point
>to a share on the original IIS Server but I'm running into a slew of
>problems. Could not get the site up.
>
>2. How do I create a share to store the images/PDFs so that both sites can
>access those items? I am running in a Workgroup so the ASP.Net account is
>specific to each machine.
>
>This seems like a pretty common requirement but I am lost.
This isn't a common scenario at all. In fact, it likely isn't ever
used. Front end servers are virtual matches to each other, with
duplicates of everything. If you want a single repository for images,
put it on a server that is shared by the front end servrs, similar to
your database server.
There are plenty of ways to replicate files, from Robocopy to
clustered servers to Application Center.
Jeff
| |
| David Wang [Msft] 2005-06-26, 7:48 am |
| As soon as you want to setup a configuration where more than one machine is
involved in servicing a request, it is no longer "simple" because from a
security perspective, neither machine trust each other (even if it is clear
to YOU that they should trust each other) and view each other as potential
man-in-the-middle attack against whatever they do.
I know that the above is not obvious to you because you just care about
getting the application working -- to heck with the security/hosting
requirements. But unfortunately, the details matter to the machines
involved, and this is where most people fail to make the realization, get
frustrated by repeated access denied or various security violations, and
ultimately settle for something which they understand but is actually a hack
and/or insecure custom solution. Unfortunately, security is not easy to
explain nor understand, but I recommend that you take time to search
microsoft.com, get the info and facts straight, and then it will look dead
simple.
You definitely need to read this URL to get a good summary of the classic
issues involved when trying to coordinate >1 machine involved in handling a
request:
http://www.microsoft.com/technet/pr...s/remstorg.mspx
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Lost With IIS" <Lost With IIS@discussions.microsoft.com> wrote in message
news:F52DE1EC-CD96-4C50-B156-8380641F6AAF@microsoft.com...
I have a relatively simple but (seemingly common) dilemma. Here is my
situation:
I have a ASP.Net/VB.Net intranet application going against SQL Server which
works great on a single IIS Server. It is a pretty straightfoward OLTP
application with a database backend and also stores images/PDFs on the
server.
I want to configure another IIS server to serve up the same content but I
don't want to have to roll out code to both servers everytime I make update.
Also, since the images/PDFs are stored on the original server, I want to be
able to access them using the second server as well (without duplicating
them).
1. How do I configure the second IIS 6.0 server so that I do not have to
roll out code to both whenever I make updates? I tried having the URL point
to a share on the original IIS Server but I'm running into a slew of
problems. Could not get the site up.
2. How do I create a share to store the images/PDFs so that both sites can
access those items? I am running in a Workgroup so the ASP.Net account is
specific to each machine.
This seems like a pretty common requirement but I am lost.
Thanks!
|
|
|
|
|