Author: Surendra Sharma | Categories: CMS selection, Sitecore CMS, CMS
This blog describes Content Delivery [CD] instance is nothing but your LIVE website.
To configure the CD environment, you must set up one or more CD instances on one or more Web servers.
Sitecore recommends that you use a dedicated Web server for every Sitecore CMS instance in the environment.
To configure an instance of Sitecore CMS in a CD environment:
<targets hint="list">
<web>web</web>
</targets>
</processor>
</initialize>
</pipelines>
<databases>
<database id="web">
<remoteEvents.listenToEvents>true</remoteEvents.listenToEvents>
</database>
</databases>
<sitecore>
<events>
<event name="indexing:start" />
<event name="indexing:start:remote" />
<event name="indexing:end">
<handler type="Sitecore.ContentSearch.Maintenance.IndexDependentHtmlCacheManager, Sitecore.ContentSearch" method="Clear" />
</event>
<event name="indexing:end:remote" >
<handler type="Sitecore.ContentSearch.Maintenance.IndexDependentHtmlCacheManager, Sitecore.ContentSearch" method="Clear" />
</event>
</events>
<crawler type="Sitecore.ContentSearch.SitecoreItemCrawler, Sitecore.ContentSearch">
<Database>web</Database>
<add name="core" connectionString="user id=sa;password=abc;Data Source=tesrsrv;Database=TestSitecore_Core"/>
<add name="web" connectionString="user id=sa;password=abc;Data Source= tesrsrv;Database=TestSitecorePub_Web"/>
To restrict access to client interfaces, disable Anonymous IIS access to all files and folders under the /sitecore folder of the Sitecore web application except to the /sitecore/service folder.
The /sitecore/service folder should be excluded from the IIS restrictions because it contains a number of service ASPX pages that are used by the Sitecore application when reporting various conditions that may occur in the application, such as, 404 Page Not Found or 500 Server Error, to the web client. So make enabled permission for service folder.