This topic is intended for administrators and developers with administration access rights in Episerver.
With this feature you can easily add and remove websites from an Episerver installation, for instance, to create short-lived campaign websites.
On the Config tab > Manage Websites, you can see an overview of all existing websites in your installation. These websites share the same database, content types and templates, making it easy to set up new websites. You can also define whether content, such as blocks and folders, should be shared or site-specific.
You have the following options to add new websites:
- Single-site setup allows your installation to have one CMS site mapped to one IIS instance. The IIS mapping is either with a wild card or a specific host name. It is possible to have several single sites with separate databases and code base on the same server. In that case, you have a separate admin interface for each site.
- Multi-site setup allows you to have a single CMS site as a base (default site), and the ability to create new sites in admin view that share the same root page, database and code base. The additional sites are either automatically mapped and require no additional configuration (if the base site is mapped to wild card), or they need manual configuration of host name.
When working in a multi-site setup, you see all sites in the same interface, which makes it easy to work with them. One reason to run a multi-site setup with specific host name mapping (that is, a different IIS instance per CMS site) is that you can use different application pools, which means that if one site goes down, the other sites continue to run.
The following requirements must be met to manage websites in admin view:
- Available licenses. A notification message informs you of the number of sites allowed by the license available for the installation. Refer to License Information on the Admin tab for detailed license information.
- Unique URL. In admin view, each website must have a unique URL and start page in the content tree. Start pages cannot be nested.
- Domain mapping must be configured in IIS.
- For multi-site setup, the IIS must be configured to respond to any host name.
- For single-site setup, each separate CMS site must have an IIS site configured.
On the Websites tab, you can click a site to see detailed information about its settings. From here, you can also update the site information.
To add more sites to your installation, click Add Site. Add the following information when creating and updating site settings for your installation:
|Name||Type a name that identifies the website, for instance, “Example Site”.|
|URL||Enter the URL for the site, for example,“http://examplesite.com”. asset|
|Start page||Select the page to which the visitor is sent if only a host name is specified.|
|Use site-specific assets||Select this check box to ensure that assetContent such as documents, videos, and images that can be linked to other content such as pages, blocks, and catalog entries in Commerce.s for this site are not available for use on other sites in the installation.|
|Host name||Optional. Enter a specific URL, for example, “examplesite.com”. If you do not name the website, it is automatically named with the URL you have entered. One of the sites in the installation must be bound to the * host name. That site is used as a fallback when an exact match for the host name used by the visitor cannot be found. This setting is less important in a single-site scenario, as you are only allowed to have one site configuration. However, in a multi-site scenario, you must make sure that all host bindings active in IIS are mirrored in the corresponding site configuration. For example, you want to add “examplesite.se”.|
|Culture||Select the default language to be used when a visitor accesses the website using the host name.|
|Type||The type indicates if a host name is the primary host, editing host, or if the host should be redirected. Redirection can be set to permanent or temporary, which determines the type of HTTP redirect status that should be used. Requests are redirected to the primary host or, if none has been defined, the first non-redirected host found. There can be one primary host name and at least one host that is not redirected or an editing host. These restrictions apply per culture and for hosts not bound to any culture. Select an edit host to identify a dedicated editing server in a multi-server solution. Only one editing host per site can be defined. Also note that the wild card host name cannot be set as primary or editing host, but it can be redirected.|
|Scheme||Select the preferred scheme that should be used for this host. This will only affect the generation of links to the site as incoming requests are matched to the host name regardless of scheme.|
The following example shows a default website with different host names, languages and redirection types configured:
This example would lead to the following behavior:
- A request to http://redirected.se is redirected to http://examplesite.se using an HTTP 301 response.
- A request to http://www.examplesite.se is served the Swedish content. Note that canonical links added in the templates should point to http://examplesite.se
- A request to http://redirected.no/page/ is redirected to http://examplesite.no/page/ using an HTTP 301 response as this is the only Norwegian host that is not redirected.
- A request to http://redirected.com is redirected to http://examplesite.com using an HTTP 302 response as per the wild card specification.
The following example shows a campaign website: