Installing Sitecore XC9 Update 1 on Azure PaaS

As part of an implementation of Sitecore 9 Update 1 (XC) on Azure PaaS, We ran into a few issues using out of the box web deployment packages and Arm templates. This post might help you address some of the issues that we have encountered and possible solutions.

Missing Assembly Bindings

If you run into a problem where Content management Complains about missing oData dlls version 6.15. This is because of missing assembly bindings in web.config

Sitecore Commerce Proxy uses 6.15 version of Odata and related dlls and they are deployed to ceconnectbin as part of the Azure Web Deployment Packages. But The Web.config from the packages do not have assembly bindings in place. To fix this problem add the below lines to runtime/assemblybinding in web.config

Commerce Engine Connectivity Issues

The following configs from the OOTB web deployment packages are disabled. We need these to be enabled for the Website to communicate with Commerce Engine

Sitecore.Commerce.Engine.Connectors.Index.Common.config
Sitecore.Commerce.Engine.Connectors.Index.Solr.config (Only required if you are using SOLR)
Sitecore.Commerce.Engine.DataProvider.config

Update Data Templates Error

Default Web Deployment Packages do not setup the Storefront. The Shop name commerce engine is configured to work with. Before running the Refresh Commerce Cache and Update Data Templates steps. Create a Tenant & Site which also sets up the Commerce Storefront that engine is configured to work with.

Enable SOLR for Azure PaaS

Enable SOLR for Sitecore

https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/search_and_indexing/walkthrough_setting_up_solr

Enable SOLR for Commerce Engine, do the following on Commerce Ops role

1. Disable PlugIn.Search.Azure.PolicySet-1.0.0.json — Change the extenstion to .disabled
2. Enable PlugIn.Search.Solr.PolicySet-1.0.0.json — remove .disabled extension
3. Replace “Entity-PolicySet-AzureSearchPolicySet” with “Entity-PolicySet-SolrSearchPolicySet”
4. Re-Bootstrap Commerce Engine using Postman and restart Commerce Engine roles so they pickup the correct configurations.

Missing Commerce User Roles

Default install did not include setup of Commerce Roles. As a result Business tools (BizFx) and Postman collection fail to communicate with commerce engine as the admin user lacks the roles that are required by Commerce Engine (Sitecore/Commerce Business User).

Add “Comerce Busness User “ to the user used for logging into Business Tools and or postman.

Missing Commerce Roles that need to be set up