Website Development Company in Singapore
⟵ Resources

Sitecore Commerce 10.2 Initial Release – Step by step Install Guide on your machine

Sitecore XP 10.0 Installation Banner

This one is a summary of my own experience for Sitecore Experience Commerce 10.2 Initial Release (aka Sitecore XC 10.2.0) installation on my machine. I’ve had much experience in the following ones:

so I decided to go only with:

I do hope that this blog post is helpful for your own journey as well.

Note: personally, I wanted to use my own install directory rather than the default one

Setup Prerequisites

Please refer to the Sitecore Experience Commerce Compatibility Table for the software and version prerequisites:

Step-by-step guide

  1. install the ones below if NOT YET
  2. rebuild the Link databases for the master and core databases if not yet:
    • on the Sitecore Launchpad, click Control Panel, and in the Database section, click Rebuild Link Databases
    • select the master and core databases and then click Rebuild
    • Rebuild link database, core and master for SC10.2
  3. rebuild the search indexes if not yet:
    • on the Sitecore Launchpad, click Control Panel, and in the Indexing section, click Indexing manager
    • in the Indexing Manager dialog box, click Select all, and then click Rebuild
    • Select all in Indexing Manager for SC10.2
  4. ensure that Experience Analytics is working properly
    • Highlight Experience AnalyticsShowing zero online interaction
    • Note: if there is any error
      • option 1: you will have to solve it before installing XC by opening the Sitecore log and then having a look at the error messages (normally, they’re certificate issues)
      • option 2: you may want to disable xDB and then fix the error later after installing XC successfully
  1. download and install the following modules to your vanilla Sitecore 10.2 instance through Installation Wizard
  2. create a new folder D:sc1020_com_install
  3. download MSBuild Microsoft Visual Studio Web targets(available from Nuget) then extract the Web targets package, copy the toolsVSToolsPathWebMicrosoft.Web.XmlTransform.dll file into D:sc1020_com_install
  4. download and unzip Packages for On Premises WDP 2021.11-8.0.218then put it into D:sc1020_com_install
  5. unzip D:sc1020_com_installSitecore.Commerce.7.0.37.zipand then rename to D:sc1020_com_installSIF for a better practice
  6. override the following files in order to inject the custom install directory of Commerce’s sites
    • open raw and then copy / paste Master_SingleServer.json into D:sc1020_com_installSIFConfigurationCommerce
    • Side-by-side code comparison
    • open raw and then copy paste CommerceEngine.json into D:sc1020_com_installSIFConfigurationCommerceCommerceEngine
    • Side-by-side comparison of the code
    • open raw and then copy / paste CommerceEngine.Instance.Deploy.json into D:sc1020_com_installSIFConfigurationCommerceCommerceEngine
    • Side-by-side comparison, showing differences
    • (optional) download + unzip  zip and then copy / paste all to D:sc1020_com_installSIF
  7. download sc1020_com_install.ps1 and put it into D:sc1020_com_installSIF then open it to correct the following parameters if necessary
    • $ScInstallDirectory
    • $SiteNamePrefix
    • $SiteHostHeaderName
    • $SitecoreDbServer
      • ensure using double-backslash if any
      • Showing the 2 backslashes in the configuration
    • $SqlUser
    • $SqlPass
    • $SolrUrl
    • $SolrRoot
    • $SolrService
    • $CommerceEngineConnectClientSecret: refer to Step 14 below
      • deployment fails if you don’t provide a qualified value for this parameter
      • Note about deployment script
  1. (optional)create a secret client certificate
    • refer to 3. Create a secret client certificate(Page 11-12) in XC Installation Guide for On Premises Solutions
    • Creating secret client certificate
    • Note: you can download the PowerShell script at Github lab and then
    • launch PowerShell as an administrator
    • change directory to D:sc1020_com_installSIF
    • execute .GenerateClientSecret
    • Highlighting the secret key
    • note the generated client script and then replace the value of $CommerceEngineConnectClientSecret
    • Highlight CommerceEngineConnectClientSecret
  2. (optional)correct the SitecoreUserNameand SitecoreUserPassword of your Sitecore XP 10.2.0 instance if you’re using others rather than the default ones
    • Showing SitecoreDomain, SitcoreUsername, and SitecoreUserPassword
  3. (optional) you can specify any local account (note: it will be created automatically if non-existent)to be set up for the various application pools that are created as part of the deployment
    • Show UserDomain, UserName, UserPassword
  4. let’s install it
    • Note: ensure that there is NO custom AllowedCorsOriginsGroup in D:sc1010_com_installSIFIdentityServerSitecore.Commerce.IdentityServer.Host.xml (they’re added automatically in prior installations) by reverting Commerce.IdentityServer.Host.xml
    • launch PowerShell as an administrator
    • change directory to D:sc1020_com_installSIF
    • execute .sc1020_com_install
    • Show cd D:sc1020_com_installSIF command
    • hopefully there is nothing can stop the installation process now
  5. open a browser then navigate to https://storefront1020.local/, you would see the default page of Sitecore website. That’s because we don’t use the default host name storefront.comso we need to correct it via Sitecore
    • log into https://storefront1020.local/sitecore/
    • access SXA Site Manager application
    • How to access SXA Site Manager
    • open Storefrontsite and then update Host Name to local and Database to master
    • Highlight storefront1020.local and master database
    • (optional) uncheck the checkbox Cache Html and select Yes for Disable Browser Caching for a better practice
    • Highlight Cache Html and disable Browser Caching
    • refresh https://storefront1020.local/ and then add some products, you would see something like this
    • Highlight storefront1020.local
  6. DO NOT forget to perform Post-Installation Steps

The recommendation

We can remove the modules completed from D:sc1020_com_installSIFConfigurationCommerceMaster_SingleServer.json and re-do Step 15 if there is something wrong (especially for Note: some known issues below) so that we are able to save a lot of time

Likewise the following one in the installation guide:

Remove a reference to a module

How to uninstall it?

  • open D:sc1020_com_installSIFps1 and uncomment the line 292 + comment out the line 289 then save it
  • Show skip.count variable
  • Note: DO NOT FORGET to restore D:sc1020_com_installSIFConfigurationCommerceMaster_SingleServer.json if you already edited it for removing the modules completed via the install operations
  • Note about SQL database server on the Commerce deployment
  • open Windows PowerShell (run as administrator)
  • change directory to D:sc1020_com_installSIF
  • execute .sc1020_com_install
  • Show responderHeader
  • hopefully, it runs well and cleans everything up

Note: some known issues

  1. ScriptHalted
    • Highlight CommerceEngine-Initialize
    • my suggestion is to remove all prior modules completed + CommerceEngine-Initialize task itself (in this case) from D:sc1020_com_installSIFConfigurationCommerceMaster_SingleServer.json and re-do Step 15

Got issues?

Please send your issues (with screenshots if possible) to so that I have a chance to understand your problem and be able to suggest the solution.

Happy Sitecore Commerce 10.2.0 Installation!

This article originally appeared on Walking on clouds (



Playing around with Sitecore 10 docker containers and my simple development framework version 3.0

How to restart Sitecore server via Sitecore user interface

Playing around with Sitecore 10.0.1 docker containers and my simple development framework version 3.1



Contact Us

Website Development Company in Singapore white logo
LowCarbonSG Logo
Terms & Conditions | Privacy Policy | Accessibility Statement

Apply Now!

Upload Resume (with a 2mb maximum file size)
Accepted file types: doc, docx, pdf, xps, Max. file size: 2 MB.
This field is for validation purposes and should be left unchanged.