11

It's easier Today if you work with Sitecore 9, you can do it from your Content Management server. Just go to /sitecore/admin/ShowConfigLayers.aspx and select Content Delivery. This is article explaining in details how to View configuration changes


11

You could use the Sitecore Config Builder to do this. It is available from the Marketplace. https://marketplace.sitecore.net/modules/sitecore_configbuilder.aspx This will allow you to view the compiled config without needing to open up the /sitecore directory for access. It also has an option to show the entire compiled web.config and not just the ...


8

If you are using Sitecore 8.0 Update 3 upwards then a couple of new default processors were added to the Health Monitors to periodically dump the Cache Status and Rendering Statistics to files on disk. By default this process is run every 10 minutes, and they are run on the CD servers as well so you can use these files to check how your caches have been ...


8

The main thing you need to set up is the Instance Names in your ScalabilitySettings.config file. The names can be anything they just need to be consistent between the CM and CD. You can leave these blank and Sitecore will create it's own unique names which can cause issues if you switch IIS sites, so it's safer if you create the names yourself. On the ...


7

Answer to this question will slightly vary on your Sitecore Version but I am listing out most common differentiating factors. If earlier both the environments were configured correctly than you can easily find out the following difference: Sitecore Admin Panel and Admin pages Mostly Sitecore Admin Panel and Admin Pages is restricted on the CDs. Hence if on ...


6

You can refer to the Sitecore Scaling Guide from SDN: https://sdn.sitecore.net/upload/sitecore7/70/scaling_guide_sc70_a4.pdf P.s. Keep in mind that http://doc.sitecore.net contains documentation only for Sitecore 8+ versions. Thus if you are looking for documentation for Sitecore versions prior to 8, you should refer to the https://sdn.sitecore.net/


5

sitecore_list_index contains the list of contacts and segmented lists that are used by the List Manager, the Email Experience Manager and the Experience Profile. More information you can find here: https://doc.sitecore.net/sitecore_experience_platform/setting_up__maintaining/search_and_indexing/indexing/search_index_descriptions On this link https://doc....


5

With Solr/Sitecore setup, you only need to enable indexing on CM, and disable it on CD servers, After any publish operation, Sitecore will try to update indexes on CD instances if the index have OnPublishEndAsync strategy enabled, Which is by default enabled on sitecore_web_index. To disable indexing on CD, you need to change the indexing strategy for each ...


5

Your CM and CD servers are available by different addresses.(e.g.: cms.test.com and www.test.com) It is possible to filter redirect rule before execution using {HTTP_HOST} variable: <rule name="Force SSL" stopProcessing="true"> <match url="(.*)" /> <conditions logicalGrouping="MatchAny"> <add input="{HTTP_HOST}" pattern="...


5

Is Saving/Updating Data from a CD Against Best Practices? Saving security/access changes from a CD is acceptable, and doesn't violate best practices. Saving data from a CD in general also doesn't violate best practices, so long as you are mindful of the data that you are saving, where it will be saved to, and that it can be overwritten (effectively ...


4

The best way to fix this would be to move to SOLR - really its the safest way to ensure that the index is the same for all delivery servers. On top of that you get additional things like the query cache, better language indexing and better scalability with Solr Cloud. If you absolutely must stay with Lucene, you could setup the CM server to build the ...


4

One option is to enable Sitecore.Speak.Mvc.Config file . In the Sitecore.Speak.Mvc.config file, the InitializeCommandRoute processor maps the /api/sitecore/{controller}/{action} route for SPEAK UI Applications, which are used by Sitecore Content Management installation. Probably your ajax call are using /api/sitecore. If there is not a specific reason ...


4

Alright, the Sitecore.ContentSearch.Azure.dll file in the CD was not (by default) the same version as in the CM. I copied the CM version to the CD bin folder and it works. (but I have no idea why the default installation puts two different files) Here is a comparison of the detail of the two dlls, LEFT: CM version, RIGHT: CD version


4

As stated in the SO answer, the real issue is that without enabling the Sitecore.Speak.MVC.config, there's no route pattern matching just {controller}/{action}. The answer that will solve your problem is that you need to enable a config on the Content Delivery Servers that enable this route. There are a couple ways you can do this: Option 1: Enable ...


4

I'm not aware of a way to do what you are asking because deny permissions are always stronger than grant permissions, so the instruction to deny access to /sitecore/* would beat the instruction to grant access to /sitecore/service/keepalive.aspx. Instead, I would recommend following Sitecore's Security Hardening Guide (section 1.5): To restrict access to ...


3

You can definitely remove Telerik, Speak, Webdav and other CM side related handlers. WebDAVRoot WebDAVRoot64 sitecore_webDAV.ashx sitecore_xaml.ashx sitecore_icon.ashx sitecore_feed.ashx sitecore_handlers.ashx Telerik_Web_UI_DialogHandler_aspx Telerik_Web_UI_SpellCheckHandler_axd Telerik_Web_UI_WebResource_axd Sitecore.SpeakJS64 Sitecore.SpeakJS32 Sitecore....


3

Obviously, the cause of this error is diverse. The error message appears when configuration define a database that is not configured or available in the environment. I had this issue with Sitecore module UrlRewrite. Please make sure that: Hi.UrlRewrite.Prefetch.Master.config is disabled in CD enviroment.


3

Adding some additional context, mentioned in other answers, the Sitecore Scaling Guide which is available on the old Sitecore Developer Network site is intended for versions of Sitecore 7.0 to 7.2. In this guide, Chapter 2.4 specifically, talks about how to convert a CM instance (which is the standard Sitecore install) and make it a content delivery server. ...


3

As Mark Gibbons already wrote in his answer, you don't want your CD servers to run any indexing. All the work should be done by CM (or Standalone) servers. Now why your code doesn't work? There may be multiple reasons here like: Sitecore.Context.Database.Name line. If onPublishEndAsync strategy is used, Sitecore.Context.Database will either throw exception ...


3

This is the support help I got and fixed it: Could you please try overriding the CheckDomainGuard processor using the following: namespace CustomNamespace { public class CustomCheckDomainGuard : Sitecore.Owin.Authentication.Pipelines.CookieAuthentication.SignedIn.CheckDomainGuard { public CustomCheckDomainGuard(BaseLog log) : base(log) ...


2

Let me start by saying that I don't think that there is going to be any one right or wrong answer to this question, but rather that this question will (and should) receive a lot of good opinion-based answers. Using IP Restrictions Instead of Disabling Access IMHO, the authentication mode should be left as-is and instead of following Sitecore's ...


2

I have encountered the same problem today while working on a function via sitecore api which is hosted in sitecore azure paas project. Hence, just to share. I have created the following: JS file <script> function showDiv() { var email = $("#email_id").val(); $.ajax({ type: "POST", url: "/api/Accounts/...


2

If you aren't able to use windows authentication for some reason, I have implemented security for the Sitecore areas on CDs by using IP filterings and only allowing the local server IP address to access the pages. This forces the user to be on the physical box (meaning they at the very least have RDP permissions, so hopefully are a trusted administrator) ...


2

@Gatogordo's "try turning it off and back on" suggestion did the trick. I found John West's All About Logging with Sitecore ASP.NET CMS blog post, which led me to an old SDN article, aptly named Wake up log files. The article poses the following problem: Occasionally after application restart log files are not working. How can I fix this without making ...


2

In my case, I had the same error when I delivered Unicorn configs to CD server. I removed all Unicorn configs from CD and added Unicorn folder with configs to my pubxml: <Target Name="ConfigFiles" BeforeTargets="ExcludeFilesFromPackage"> <ItemGroup> <ExcludeFromPackageFolders Include="App_Config\Include\Unicorn"> <...


2

Virtual user information is saved in Session. By default Sitecore configuration doesn't share sessions information between few CD servers. That is why one CD server doesn't know anything about logged in users on others CD servers. You have few options, how to solve it: Configure your hosting environment to use sticky load balancer. Link that was mentioned ...


2

Just brainstorming here, but one way of approaching this would be to go with a 'multisite' scenario, which could be risky depending on how many hard-coded GUIDs you are using. A secondary site with the new structure and content can be set up, completely published, and ready to go. When you are ready to swap, the host mappings can be updated so your new ...


2

In default Sitecore installation, this settings is not even used. Sitecore.Publishing.Pipelines.Publish.OverridePublishContext processor overrides it anyway. It's only when this processor is disabled, the settings is used. But even then, only the publishing server is affected. From what I know, CD server does not "receive" the published context, it only ...


2

You have "master" database configuration on your CD server. It requires "master" connection string that is absent. You can remove master database (<database id="master") configuration on your CD server to overcome this issue. (or if you need for some reason master database on your CD server, then add connection string to master database in you ...


2

Sitecore has been very specific that Lucene should not be used in scaled out environments. This is because every CD may have a different index, and demonstrate the issue that you are reporting. Sitecore's own documentation says: You must use Solr if you have a scaled environment. The recommendation to fix this issue is to install Solr and have all CD's ...


Only top voted, non community-wiki answers of a minimum length are eligible