Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
This topic describes the deployment of Episerver Commerce solutions. The topic's sections describe the commerce-specific tasks needed to verify a successful deployment. See also the Deployment section in the Episerver CMS Developer Guide for a general understanding of how to deploy Episerver solutions.
Implement reliable, scheduled backups for the Episerver Commerce Application and the database using SQL backup jobs.
If you push changes made on a development and test/QA environment, then copy web files to the production server and ensure that each config file is pointing to the correct server. For example, you can copy web files to a new server with Richcopy, a powerful GUI wrapper for Robocopy, the standard file duplication command-line utility included with Windows and Windows Server. Other copy utilities are available; be sure your utility suits your needs.
When you deploy .NET sites on the production server, you need the non-compiled files, such as *.asax; *.aspx; *.ascx; *.asmx; *.gif; *.jpg; *.html; *.js; *.xml; *.png; *.css and so on. You also need to transfer the files in the /bin directory, which is where the compiled code is. Also, do not forget any updated configuration files.
You do not need the *.cs and *.resx files. Also, you do not need the *.pdb files (debug files) in the /bin directory.
You need the built-in ECF directories but these directories only need to be deployed once, unless you make changes to them. However, you should not change the built-in directories because they get updated if you upgrade the ECF application later.
When you update an ECF site later on and made changes only to the server-side code, you need to deploy only the custom dlls in the bin catalog on the production server. If you make any changes to the aspx/ascx files, you also have to deploy those files.
Note: When the site is recompiled, transfer the updated dlls. When the HTML code is changed, transfer the updated *.aspx or *.ascx files. If changes are made to both dlls and HTML, transfer both.
After your site is deployed, protect and secure your deployment with the following high-level security checks to ensure that Commerce Manager is restricted to only authorized users.
Each website that handles personal data should have SSL security to encrypt traffic and secure customer information. This is especially important when customers are checking out and purchasing items directly from the site.
Last updated: Oct 12, 2015