Since the default install for Sitecore Experience Commerce 9 separates IIS sites for all roles (Authoring, Shops, Ops, Minions), updating some hard coded configuration parameters in the Sitecore.Commerce.Engine.2.2.126.zip package before running the DeployCommerceEngine task will save you some time. Otherwise, you will have to individually update the content on all 4 roles.
1. Extract Sitecore.Commerce.Engine.2.2.126.zip
2. Update environment configuration files:
After extracting the zip file, under Sitecore.Commerce.Engine.2.2.126\wwwroot\data\Environments, you will see a bunch of JSON configuration files. In addition to the standard environment configs, there also policy sets that these environment configs reference. The following changes may be required:
These files are sample Habitat environment configs. You will need to rename these files from Habitat to your specific instance and update/keep/take out values based on your specific environment configuration. Don’t forget to rename all Habitat variables to your own naming convention. Most of the settings here will be different based on your specific setup, e.g. your specific policies.
If you are not using Windows authentication, e.g. in a scaled architecture, update the following parameters to use SQL authentication instead:
TrustedConnection. Set to false.
UserName and Password. Corresponding to your SQL authentication user.
Update the Password for the Sitecore admin user.
3. Update Global.json in the bootstrap folder:
Update SQL server parameters under EntityStoreSqlPolicy (TrustedConnection to false, UserName, Password)
If you are using the sample Migration plugin, update the SQL server parameters for the source database under Plugin.Sample.Upgrade.MigrationSqlPolicy
Update Sitecore admin Password under SitecoreConnectionPolicy
4. Zip the extracted folder and overwrite the original Sitecore.Commerce.Engine.2.2.126.zip
Now when you run DeployCommerceEngine, you can sit back and relax knowing you did the right thing.