This blog post describes EPiServer CMO installation and configuration in a load balanced environment where CMS editing interfaces and components are not available on the front-end web servers; additional editing server is set up and attached to the same database. This kind of environment is described in this blog post as Option 2. So let’s
Load balancing is a clear choice for the most of popular sites with high volumes of incoming traffic. This solution allows distributing the load among several servers to improve performance and achieve high availability. This blog post describes а simple case of EPiServer CMO installation and configuration in the hosting environment where load balancing is
This blog post describes several options for advanced EPiServer CMO deployment. You may have more than one server, for example when site database is hosted on the separate back-end machine. You can consider the following options to distribute the work across servers: CMO database on the separate server. It sounds logical to keep CMO database
Running EPiServerCMO.msi you get CMO installed to EPiServer CMS module folder, by default it is C:\Program Files (x86)\EPiServer\CMS\6.1.379.0\Install\Modules\CMO2.1.0.93. Now it can be installed on specific web site using Deployment Center. Installation instructions for EPiServer CMO 2 R2 pretty well describe simple deployment model with the one front server. By default all CMO components are deployed