This is an addition to Kyles answer. While you can do the full site definition for each site, it quickly becomes cumbersome and really for most of the settings you have the same values.
So you can use property inheritance in the patch file. For example if we have 4 sites, we can create the first one with fill definitions, but for the others, we can just ...
You can configure Sitecore to respond to requests with different home nodes based on the url.
To do so, you need to perform the following steps:
Configure DNS appropriately.
Add a binding in IIS for each hostname.
Copy or rename the config file App_Config/Include/SiteDefinition.config.example to App_Config/Include/SiteDefinition.config
Modify the config ...
This is one of those questions where there are multiple answers available. The answer above by Kyle Trauberman is the default, configuration way that Sitecore provides to do multiple sites. It has it's pro's and con's.
There are also a handful of modules on the Sitecore Marketplace, such as Dynamic Sites Manager, that provide the ability to create sites ...
Can you please check your /sitecore/admin/showconfig.aspx file to see if the above patched site definitions exists there and they are before the "website" site definition ?
Also check Language.AlwaysStripLanguage setting in ShowConfig.aspx also set to false.
If above options are correctly done, then please check if your "website" site definition have any ...
As the other comments have mentioned the hostnames in the config need configuring however alongside that there are quite a lot of things to consider for multi-site in Sitecore and the difficulty of getting it to work depends on if it was considered in the initial build or not.
I'll jot down some bits and pieces to consider, especially in the scenario where ...
Sitecore is not designed to work with multiple individual instances in a single AppDomain. @RichardSeal reminded me that it makes use of shared (singleton) objects that would conflict between the two applications. These are used to improve performance and aid in caching certain resources, but make coexistence of two applications impossible.
ClusterName is a value of the cluster address to which a server belongs. The name should be identical for all content delivery servers that are in the same cluster. I usually use a string here, not a hosname. I believe this has nothing to do with multisites URLs.
EXM documentation states:
Ensure that the value of the Analytics.ClusterName setting is ...
This is a loaded question and the answer will wholly depend on specific situations and several factors such as security, performance, code-dependency, deployment scenarios, uptime requirements, etc. There are several blogs out there about multi-tenancy and multi-sites (plus multi-languages/regions) but here's one that Sitecore is evangelizing through Helix.
As far as i know, Sitecore does not recommend this, Some issues you might run into :
If your site have access to master Database and tries to update items, these updates will not be synced between all the Multi IIS sites because each IIS site will have its own inconsistent memory cache.
Each IIS site will have its own Sitecore memory cache of item/media ...
This might be slightly off topic, but I can give you a bit of background info.
In EXM 3.3 you can move/change the email open handler by modifying the configuration setting EXM.OpenHandlerPath in Sitecore.EmailExperience.Core.config.
The EXM 3.3 open handler does not require the tracker. It creates an interaction using the interaction registry. See Register ...
Configure the site node in IIS to add the new host name binding.
Create a patch file to patch in a site node to the /sitecore/sites configuration section.
You can customize Sitecore analytics, but you should first break down some requirements for what you want to see within Sitecore Analytics dashboard, and who should see it.
Assume you have a multi-tenant setup like this:
Out of the box, Sitecore analytics collects data per site and allows you to filter per ...