This technique is not recommended for production instances. The ideal use-case is to quickly spin up sandbox environments or non-prod environments. Once this deployment is complete, the standard Sitecore install process can be followed with no tinkering of Solr: Azure Quick Start ARM templates or via Sitecore Experience Cloud Azure resource.
Install Solr as an App Service in about 10 minutes preconfigured for Sitecore 8.2u7+. Click the button above and follow the prompts. Be sure to select the proper Solr Version for your Sitecore installation (https://kb.sitecore.net/articles/227897). Once this deployment completes, all prerequisites for Sitecore are in place. You may run quick start templates or install directly from "Sitecore Experience Cloud" Azure resource and provide the Solr link, e.g. https://myappservice.dev.azure.net/solr. Full credit goes to Dan Cruickshank. His guide was used as the basis for this one-click deployment:
https://getfishtank.ca/blog/installing-solr-app-service-in-sitecore-azure-paas
POST-INSTALL: Populate managed schema (control panel) for all indexes.
This script sets the httpsOnly
property to true
by default, but it can be modified in the parameters (in the prompts).
- [Deploy to Azure] button looks for
azuredeploy.json
file at repo root azuredeploy.json
deploys resources. Notable steps listed below:solrVersion
parameter is added as anappSetting
to the web app. This is required to parameterize it when callingDeploy-SolrAzureAppService.ps1
web > config
resource. SetsjavaVersion
to 1.8 which supports all (?) Solr versionssourcecontrols
resource. This is the brains of the operation. It deploys THIS repository to your web app.- With this resource deployment, if a file named
.deployment
exists at the repo root, it is executed once the repo has been cloned to your web app
- With this resource deployment, if a file named
- The
.deployment
file callsDeploy-SolrAzureAppService.ps1
with the Solr version as a parameter (parameters are only accessible from the.deployment
file). Deploy-SolrAzureAppService.ps1
is where the majority of work occurs. This is where Dan's manual work was implemented in an automated fashion- This script downloads and extracts the desired Solr version to the web root
- It also copies the
web.config
from the repo to the web root
To see the deployment logs, find your deployed App Service in Azure, then in the left-hand navigation select Development Tools > Advanced Tools (Kudu)
, then click Go
to launch Kudu. Once Kudu launches in a new tab, from the primary navigation select Tools > Zip Push Deploy
. Once this page loads, expand the deployment steps at the bottom to see the log output and any errors.