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\CMO126.96.36.199. 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 on the same machine and you get the following deployment schema:
Main EPiServer CMO components are described bellow to make this chart clearer.
EPiServer CMO components
It’s worth mentioning that it’s not about assemblies. Components are EPiServer CMO parts that communicate and cooperate with each other, these parts can be separated logically or/and by deployment.
Core is the heart of EPiServer CMO, all other parts depend on it. This is the central component that contains core logic for collecting and processing data.
CMO Statistics Handler
This component receives and processes raw visitor’s statistics and KPI data coming from client browsers.
CMO Web services
Currently CMO provides one web service that can be used by third party applications to update KPI values.
This is storage for EPiServer CMO data. By default it is separate database, but it is possible to create CMO data structures in the existing one.
CMO Aggregation Service
This is Windows service application responsible for data pre-calculation and aggregation. It allows to decrease database size and generate reports faster. The one Aggregation Service is able to process data from different CMO versions and can serve the number of CMO instances deployed on several sites.
CMO Thumbnail Service
This is Windows service application, which creates screenshots of site pages and provides thumbnails for reports. Check out this blog post for more information about CMO Thumbnail service.
CMO UI is user interface available for CMO administrators and users to manage LPO tests and campaigns, view reports, monitor statistics and configure settings.
CMO UI pages and resources are not copied on site during installation; it is connected via virtual path provider in the same way as CMS Edit/Admin UI.
After installation steps
Depending on your environment you may have to complete these additional steps after installation.
- If you are going to run web site on .NET 4, please see Configuring EPiServer CMO 2 R2 to Support .NET 4.0
- Configure CMO Live Monitor for multiple bindings
- CMO Thumbnail service requires additional configurationif it is installed on Windows Server 2008 R2
- See Configuring after installation section in Installation instructions.
- Check access permissions in CMO Settings / Security page. By default only users in Administrators, WebAdmins or WebEditors roles have access to CMO UI and can manage the module.
Notes and tips
- Friendly URL Rewrite module is required on site. CMO uses Friendly URL Rewriter events to inject scripts that collect visitor’s statistics.
- View State must be enabled at least for CMO location.
- If you face the exception related to ComponentArt stuff, try IIS reset.
- Delete EPiServer.Cmo.Wizard.dll assembly if it exists in the bin folder of your site.