1. Deploying sample sites

SCpbMD Reference storefront

Version:

Before you set up the SCpbMD Reference Storefront, ensure that you already gone through the Single Server SCpbMD install, or set up SCpbMD on a CM or CD server. The released package for SCpbMD is found on GitHub. Within the zip file:

  1. The Database folder contains all of the artifacts related for configuring the Commerce Server site and

  2. The Packages folder contains all of the artifacts related for configuring Sitecore.

The setup steps are as follows:

  1. Install Contoso Images:

    1. Navigate to http://<your site>/sitecore/admin/UpdateInstallationWizard.aspx, and follow the steps in the wizard.

    2. Upload the ContososImages-1 update file.

      • The Contoso images update package are located on dev.sitecore.net under the Microsoft Dynamics section.

  2. Install Sitecore Reference Storefront powered by Microsoft Dynamics:

    1. Navigate to http://<your site>/sitecore/admin/UpdateInstallationWizard.aspx, and follow the steps in the wizard

    2. . Upload the Sitecore.Reference.Storefront.Common update file.

    3. Upload the Sitecore.Reference.Storefront.Powered.by.Microsoft.Dynamics update file.

  3. Merge the $\Website\MergeFiles\Merge.Commerce.Storefront.config into the web.config.

  4. Expand the Sitecore.Reference.Storefront.for.SCpbMD.<version>.zip file

  5. UnPup the Commerce Server site.

    1. Install the \Database\pup\SolutionStorefront.pup by double clicking it, or opening the Commerce Server Site Packager and selecting the pup file.

    2. Select Custom unpack.

    3. Set the Site name to SolutionStorefrontSite.

      • If you choose a name other than SolutionStorefrontSite. you will need to update the siteName attribute on the CommerceServer element in the web.config to match this name.

    4. Only select Product Catalog as the resource to unpack. SCpbMD does not interact any other part of Commerce Server.

    5. Click next on the Global Resource Pointers page.

    6. On the Database Connection Strings page update the server name if you are not using a local SQL server, then click Next.

    7. On the Select Applications page make sure SolutionStorefrontSite_CatalogWebService is the only application selected and then click Next.

    8. On the Select IIS Computers, Web Sites and Paths page update the IIS Web Site target for the Catalog web service if you are not using the default, then click Next.

  6. Secure the Commerce Server resources:

    1. Update the web service app pools accounts.

    2. Add the expected Desktop Business Tool users into the various AzMan files.

    3. Lock down the Commerce Server databases with the accounts from the web service and site app pools.

      • You can secure the Commerce Server databases manually, or you can use the \Database\Security\CommerceServer_Security.sql file as a helper. Search the document to replace the database names and user names with yours, and then run the SQL file against your database server.

  7. Import Catalog:

    • Use Catalog Manager or ImportCatalog.exe to import:

      • The catalog data and schema file \Database\Catalog\Sitecore Commerce Reference Storefront for Dynamics Sample Catalog.xml.

  8. Do an IISReset and then log into Sitecore.

  9. Expose Commerce Server catalogs in the tree.

  10. Publish all content to Web.

  11. Index all content.

If you have a separate Processing server, then you need to deploy the Reference Storefront update package on that server, because it has a processor in the Initialize pipeline that needs to register some types with MongoDB.

If you have suggestions for improving this article, let us know!