Sitecore Pantar

  Automated Maintenance Heath status check and Auto heal Health Status In order automatically monitor the application’s health status, Health check feature was enabled. Using this feature there will be a ping to the specified health check path on all instances of the webapp every 2 minutes. If any web app instance does not respond within 10 minutes (5 pings), the instance is determined to be  unhealthy  and instance of the webapp will be taken out of the load balancer. The health probe will continue on the instance even though it is out of load balancer. Once the health probe receives a valid response, the instance will be added back into load balancer. Steps to enable the feature, 1.        Open the Resource explorer from the App Service blade in the portal under Development Tools. 2.        The resource explorer will open to the top-level view of your App Service. Expand the config section and c...

  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...