This content is archived. See latest version here

Last updated: Oct 21 2014

A single server deployment is composed of an EPiServer Commerce solution deployed to a single computer. EPiServer Commerce can be scaled for single server deployments, typically reserved for applications and web sites with modest demands and requirements. The basic requirement for EPiServer Commerce is a database for storing customer, user, and site information which can be installed on the same or separate server as the EPiServer Commerce web application. This type of deployment can also be considered "non-distributed deployment" because all layers and functionality of an application resides in a single server.

Much of the tasks used to install EPiServer Commerce for development applies when deploying to a single server. Refer to the installation instructions for more information on how to install.

System requirements

Ensure that the deployment server satisfies the System Requirements.

Single server deployment architecture

This is an overall picture of how a typical single server deployment is laid out.

Single Server Deployment

Installing EPiServer Commerce

You can simply copy over the entire installation of EPiServer Commerce from a QA/staging server and update the configuration files and IIS on the target server. Unlike a development or QA/staging server, the deployment server should be configured via IIS to be publicly accessible.

Verifying and testing

If you have able to connect and see the public front-end site on the deployment server, then you have successfully deployed EPiServer Commerce.

See also


Do you have feedback on this documentation? Send an email to documentation@episerver.com. For development-related questions and discussions, refer to our Forums on https://world.episerver.com/forum/