I have to set two web sites on the same IIS 7.5.
One of them is Classic ASP with MSAccess Database. The other one is ASP.NET. Meaning they will use different Application Pools.
I only have one port open : 80.
How can this be configured?
Thanks.
You can create 2 applications under the same website using the same port (80).
Each one can have different Application Pool.
This way, to browse applications, you will type
http://mywebsite/app1
http://mywebsite/app2
Otherwise you can have 2 different websites using the same port, but this involves configuring host header bindings over IIS and creating C-NAME record in your DNS
This way, to browse applications, you will type
http://app1.mydomain.com
http://app2.mydomain.com
You need to configure host headers ("Bindings") in IIS for your first site before you can open the second. In other words you have to tell IIS which hostname leads to the first website, cause you can't run 2 websites as "default" hostname.
Related
I have two sites configured on my IIS 7 server. One is the default web site and the other we will call www.othersite.com. The default web site runs a few different Applications running ASP.NET and the other site is a ColdFusion 8 web site.
The default site is configured to pull from the default web location at C:\inetpub\wwwroot while the other is set to pull from C:\sites\othersite.
The bindings are set to send all unassigned traffic to the Default Web Site, but www.othersite.com is set to a specific IP address. This is the same as I have it on other servers, which work perfectly well, but for some reason when I load www.othersite.com it is looking for its files in C:\inetpub\wwwroot instead of C:\sites\othersite even though the physical path is clearly defined in the basic settings.
Anyone have any idea why this might be and how I can get it to point to the proper directory?
Under IIS >> Bindings, you can see a place to put in "Host name". Leaving blank will result in all traffic to IP or host, but by specifying a host name (www.othersite.com) will direct traffic to that dir/site.
Can I host different host address web sites on port 80 in default website in IIS 7.5 by creating applications ? Or Do I need to create separate websites in IIS with port 80?
Any good documentation, please provide me. I need to host www.WebsiteA.com and www.WebsiteB.com on port 80. I was in the impression of using single website host different websites.
If you want them to look like this: www.WebsiteA.com and www.WebsiteB.com
Then you have to create different websites.
Different applications are used in case you have the same host header and want your url be like: www.WebsiteA.com/app1 and www.WebsiteA.com/app2
Here are some technet links that can give you more insight
Add a binding to a site IIS 7
http://technet.microsoft.com/en-us/library/cc731692(v=ws.10).aspx
Configure a Host Header for a Web Site (IIS 7)
http://technet.microsoft.com/en-us/library/cc753195(v=ws.10).aspx
Managing Sites in IIS 7
http://technet.microsoft.com/en-us/library/cc771341(v=ws.10).aspx
I am new to the web world, so I apologize if this question is silly.
I have an ASP.NET web site I wish to deploy.
The server has IIS 7 deployed on it, and I've added the site
to that IIS server as a web site.
For the time being I don't have a domain mapped to the site,
I would like the users to browse for the site directly by using the server's IP.
Is that even possible? because I failed to do it.
The only option that worked so far is using the hosts file to declare
a fake domain.
It would be nice if someone could clarify that issue for me.
Thanks a lot,
Omer
If you set the site bindings to IP address: All Unassigned on port 80, and do not provide a host name, then any request that makes it through to IIS should be served by that site. Make sure you stop any other sites that might have that binding (e.g., "Default Web Site" is normally bound to this).
In order to access the site by IP, you can't have the host name populated in IIS. Your best bet would be to use the "Default Web Site" that's already in IIS, and point that to your application.
Using IP is possible, but you need to make sure your users can see this ip from their machines.
Is it possible to have a web service within an ASP.NET forms web site run on a different port, sort of like how SSL has a dedicated port?
The service needs to see the app_code folder in the existing site and of course app_data.
Any links to articles or tutorials would be greatly appreciated.
You can have several different ports bound to a website in IIS, however if you bind that port, it will work on the whole website. You can't bind a port specifically to a directory within a site.
So you can have a secondary port (ex: 8080) added along with a hostname through the website bindings in IIS.
If you don't want to have the rest of the site (that's not the web service) to respond to the secondary port, you would have to do it through either code, or configuration.
I have a Continuous Integration server with dozens of ASP.NET applications hosted on IIS. Everytime I want to deploy a new application, I have to create a new Website or virtual Directory and configure it as an application in IIS.
I would really love to have only one website listening in a specific port (say, 80) serving multiple ASP.NET sites according to wildcard host headers.
For instance:
*.dev.mydomain.int -> my server's ip address (eg: 192.168.1.32)
IIS web site reads the host header and try to find a local folder with the same name. Ex: when a request uses the host header "helloworld.dev.mydomain.int" IIS tries to open a preconfigured folder appending the host header site name (e.g: D:\dev\helloworld)
IIS serves the contents of the folder as an ASP.NET application, using preset configurations (Application Pool, ASP.NET version, and so on).
My goal here is not to create a web site or virtual directory for each and every project in our CI server. I know I can create them programmatically, but I'd prefer a more dynamic solution.
Thanks in advance
You can use MSBuild tasks to create Virtual Directories / Web sites automatically.
http://fczaja.blogspot.com/2009/02/automatic-deployment-of-webapp-on-iis.html
I had it working on a large application with many branches (we had an environment for each branch) and I didn't have to open IIS settings at all. Just pure hands-off process.