Sitecore Commerce 8.2.1 Installation Guide for Reference Storefront-Part 3

Sitecore Commerce 8.2.1 Installation Guide for Reference Storefront-Part 3

Install Sitecore Experience Platform


Follow the Sitecore XP Installation Guide for installing dependent software, and for installing Sitecore XP from the Sitecore 8.2 rev. xxxxxx.exe file.

  • Install clean sitecore instance and name it as storefront.Instance name can be choosed as per your needs.

  • After you have installed Sitecore XP, change the Sitecore web site's application pool identity to .\CSFndRuntimeUser.

  • Navigate to IIS and Navigate to the application pool of your xp instance(storefront)

  • By default application pool identity will be in network service,Change it to .\CSFndRuntimeUser.

  • Click the application pool of your xp instance(storefrontAppPool) and click on "Advanced Settings" in Actions Pane

  • AppPoolIdentity

  • click on the Identity and change the Identity.Prefix the application pool identity with “.\”

  • Click on Custom account

  • Custom account

  • Set the identity to CSFndRuntimeUser.Prefix the application pool identity with “.\” and click ok.

  • user for app pool

  • Launch your sitecore instance


Additional Sitecore XP configuration



After you have installed the Sitecore Experience Platform, there are some additional configuration steps required to set up the Sitecore site with bindings and HTTPS.




  1. If you want to use a different domain for the Reference Storefront other than the default (http://cf.reference.storefront.com), you must update the hostName attribute of the storefront site node in the Website\App_Config\Include\Reference.Storefront\Reference.Storefront.config file. This file will be deployed in a later step.

  2. Add an entry for 127.0.0.1 cf.reference.storefront.com to the the hosts file (located at C:\Windows\System32\drivers\etc\). This allows you to access the Sitecore site at http://cf.reference.storefront.com/.

  3. Set up a Self-Signed certificate that you can associate with the site to support HTTPS. (The Reference  https://technet.microsoft.com/en-us/library/ff710475(v=ws.10).aspx . Use the domain name for the name of the certificate.In my case i created Self Signed certificate with the name "storefront".

  4. Add HTTPS binding for your commerce instance with your created domain.In my case i created self signed cerficate with name "storefront".So i added https binding as storefront and choosed storefront in SSL certificate

  5. Add bindings for cf.reference.storefront.com to the Sitecore site in IIS Manager. Add one HTTP binding using port 80, and one HTTPS binding on port 443 with the Self-Signed certificate. Set the host name for both bindings to cf.reference.storefront.com.



For Successful commerce installation Continue Reading https://xchangesitecore.com/sitecore-commerce-8-2-1-installation-guide-for-reference-storefront-part-3/ Vikash Raaj

Comments

Post a Comment

Popular posts from this blog

Handling Disaster Recovery Plan

Image
Handling Disaster Recovery Plan We all are interested in knowing how to make the disaster or backup production environment which can help to reduce the downtime in real world. We need to setup the servers in different regions. mirror the database to each region from live environment load balancer should be configured to route the request to other environment if the server reachable or alive test page doesn't respond or its 404 bad response. Intimate the network and IT team about failures. Once the original environment is up, request can be sent to the original servers and the mirroring regions can be kept alive and as cold stand by. https://xchangesitecore.com/handling-disaster-recovery-plan/ Vikash Raaj
Read more

Sitecore Media Library

Image
Sitecore Media Library Controlling File Upload and Deny Execute Permissions on the Upload Folder You can strengthen the sitecore installation by restricting the access to the files that are begin uploaded by users. If you allow users to modify the content of /upload in website root folder then you also give them permission to place the scripts and executable programs. Executing these scripts and programs can cause an unexpected behavior on the server. You must therefore prevent an uploaded file from being executed on the server side when a user attempts to download it. We recommend that you deny permissions to run scripts and executable files in the /upload folder Note: You only need to perform this step if your configuration allows content authors to place files directly to the /upload folder. For example, if you use a shared directory or FTP server, content authors can quickly place a lot of media in the media library. Denying Execute Permission in IIS yo...
Read more

Sitecore Aliases for Multi Site

Image
Sitecore Aliases for Multi Site Are you having multi site environment and want to make use of Aliases in different for each site and\or share the Aliases for couple of sites? Yes we can do with the help of the custom plugin that was built to extend the feature of the Aliases Aliases for Multi-Site Environment https://xchangesitecore.com/sitecore-aliases-for-multi-site/ Vikash Raaj
Read more