Disclaimer: This website requires Please enable JavaScript in your browser settings for the best experience.

HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideLegal TermsGitHubNuGetDev CommunityOptimizely AcademySubmit a ticketLog In
Dev Guide

Single-server deployment

Describes the deployment of the Optimizely Commerce Connect 13 solution on a single computer.

A single-server deployment is an Optimizely Commerce Connect solution deployed to a single computer. You can scale Commerce Connect for single-server deployments, typically reserved for applications and websites with modest demands and requirements. The basic requirement for Commerce Connect is a database for storing customer, user, and site information that you can install on the same or separate server as the Commerce Connect web application. Consider this type of deployment a non-distributed deployment, because the application's layers and functionality reside in a single server.

Many tasks used to install Commerce Connect for development apply when you deploy to a single server. See the installation instructions to install and the System Requirements.

The following is a typical single-server deployment.

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

If you can connect and see the public front-end site on the deployment server, you successfully deployed Commerce Connect.