A default Sitecore installation defines a single published web site. However, Sitecore ships with a number of logical web sites defined in web.config. These are;
- shell - The main Sitecore client site
- login - Sitecore client login page site
- testing - Reserved for internal use. Used for solution testing
- admin - Secures some administrator tools, such as the dbbrowser and the cache manager
- modules_shell - Reserved for internal use. Used internally by modules
- modules_website - reserved for modules usage, front-end side
- website - default front-end web site, also used for WebEdit, Debug, Preview
- scheduler - reserved for system background jobs, e.g.: scheduled tasks execution
- system - reserved for system background jobs, e.g.: Lucene index updating job
- publisher - reserved for system background jobs, e.g.: publishing operations
A single Sitecore installation, however, is capable of publishing any number of web sites, each with its own properties. The properties for each site are, by default, stored in the Sitecore web.config file.
The Sitecore web.config file includes a list of served web sites listed in the <sites> section. Sitecore parses incoming HTTP requests and selects the appropriate site based on the HTTP request parameters.
The approach described in the present article works well for solutions which serve few sites and where the list of sites does not change often.
Some installations, however, need to support many sites or change the list of supported sites often. In this case, changing the web.config file for each new site is unacceptable for a number of reasons:
- Every change causes a web server restart.
- It increases the possibility of errors, which can lead to additional server downtime.
- It takes the time of a Sitecore Administrator.
A custom module for defining and resolving sites can be built in Sitecore, thus allowing the avoidance of the web.config file change for each site added. The Multiple Sites Manager module found in the Shared Source Library provides such solution.
This section describes the process of configuring an extra site in the web.config file
This section describes the process of adding a new site
From time to time, users running a multisite solution are faced with the desire to have an IIS logfile for each domain for statistics purposes.
Sitecore automatically parses the incoming HTTP request to resolve which site information it should use
A list of known issues concerning the material of the article