I assume you are talking about multiple web sites using a single database as backend. Although not tested yet, this should be possible with the current beta version. For the purpose you will need to make a copy of the root folder, and create a new virtual folder in IIS for the second web site. Note that you can’t use SQL Express to test this as it allows only one connection at a time.
Next, you need to specify the same connection string for both sites and different application names for the CMS data provider in the web.config file.
<cms defaultProvider="NolicsCmsProvider" allowPageHistory="true" allowPageWorkflow="true">
<add name="NolicsCmsProvider" applicationName="App-1" connectionStringName="DefaultNolicsConnection" type="Telerik.Cms.NolicsCmsProvider, Telerik.Cms"/>
If you specify the same application name for both sites, they will operate with the same data and therefore everything will act as one site. A very important thing to consider here is changing the application names. If you change the name of an application after entering and saving some data, this data will not be visible and the site will look like a brand new one, without any pages and content. If the no application name is specified, the default parameter is “/”.
The same thing applies to each module, although they can work in separate databases as well.
There will be a detailed description for the data provider settings in the documentation for the final release.