Sitecore Pantar

  Common Issues and solutions: Sitecore Issues a.        Indexes not building in CD server. Root Cause: Config has Instance name explicitly mentioned. This instance will certainly not match to Instance name in Azure App Service as the instance name are dynamically created. This was found by inspecting EventQueue Table in Core Database The instance name is mentioned in this config on CD server. App_Config\Include\<SomeFolder>\SwitchMasterToWeb.config The solution is to Empty the Instance Name so that it takes the default Azure App Service resolved Name. Now on re-indexing you can see dynamic Instance Name b.       Rebuild index failure due to high CPU usage on AppService High CPU usage (above 70-80%) was observed when trying to rebuild index for core database. So as and when the CPU reached high usage the Sitecore instance itself getting shutdown and failing the index rebuild process. As t...

  Sitecore - On-Premises to Azure PaaS (ASE) Cloud Migration - Part 2   Security aspects considered while designing the new Azure PaaS infrastructure   Sitecore Web applications are hosted inside Azure App Service Environment (ASE) which is an Azure App Service feature that provides a fully isolated, dedicated and secure environment to run App Service applications    WAF protection o    WAF feature of the Application Gateway provides centralized protection for your web applications from common exploits and vulnerabilities. o    WAF is based on rules from the Open Web Application Security Project (OWASP) core rule sets 3.0 or 2.2.9. o    Sitecore Content Delivery server runs behind WAF and IP restrictions on the Web App. These limits access only from the Application Gateway ·          With Application Gateway, only IPs from certain countries were allowed (based on previous ...

  Sitecore - On-Premises to Azure PaaS(ASE) Cloud Migration - Part 1 Introduction In this blog series, I’ll attempt to explain in the detail the architecture, design and approach for migrating (or should I say Re-hosting) a Sitecore website from an on-premises environment to Azure PaaS ASE environment.   Background The current Sitecore website hosted on on-premises had scalability issues. The website performance was impacted during the spikes in demand. The Traffic volumes coming into the website was expected the double due to a merger. The desired objective was to scale website to enough level to cater for increased volumes and Improve the existing resilience levels of the website. On-premises Architecture Highlights of the current on premises architecture Sitecore version 8.2, Mongo DB for Analytics and Backend systems were Oracle and .NET based There were 6 Sitecore Content Delivery servers split across 2 Data centers Three in each of Data Center (Windows 20...