- BLOB providers
- Client resources
- Configuring .NET SignalR
- Configuring episerver
- Configuring episerver.basicAuthentication
- Configuring episerver.dataStore
- Configuring episerver.framework
- Configuring episerver.packaging
- Configuring episerver.search
- Configuring episerver.shell
- Configuring Image Service
- Configuring link validation
- Configuring Live Monitor
- Configuring module.config
- Configuring staticFile
- Reading application settings programmatically
- Selecting content
- Refactoring content type classes
- Persisting IContent instances
- Block types and templates
- Content Type attributes
- Converting page types for pages
- Creating a page programmatically
- Creating page templates and block controls
- Edit hints in MVC
- IContentRepository/DataFactory interface
- Localizing the user interface
- Page types and templates
- Assets and media
- Dynamic content
- Dynamic data store
- EPiServer CMO
- Event management
- Scheduled jobs
- About EPiServer Full-Text Search Client
- About EPiServer Full-Text Search Service
- Adding search providers
- Configuring EPiServer Full-Text Search Client
- Configuring EPiServer Full-Text Search Service
- Installing and deploying Search Service
- Search integration
- Searching and filtering
- Searching for pages based on page type
- AspNet Identity OWIN authentication
- Authentication and authorization
- Configuring Active Directory membership provider
- Configuring Web Services authentication
- Federated security
- Forms authentication
- Managing cookies on the website
- Mixed mode OWIN authentication
- OWIN authentication
- Permissions to functions
- Protecting users from session hijacking
- Recommendations for ASP.NET security settings
- Securing edit and admin user interfaces
- Virtual roles
- User interface
- Context-sensitive components
- Creating a component
- Describing content in the UI
- Developing gadgets
- Extending edit view
- Extending the navigation
- Introduction to Dojo
- Message service pool
- Publish and subscribe messaging system
- Service locator
- Shell profile
- Store architecture
- Technical overview
- Using jQuery
- Command Pattern
- Object editing
- Virtual path providers
This content is retired. See latest version here.
Last updated: Mar 31 2014
Note: This topic has no later version.
EPiServer Campaign Monitor and Optimization (CMO) is a module for measuring and monitoring campaigns, as well as optimizing landing pages. The CMO module is included with the EPiServer installation package, and in this section it is described how to set up the various parts of CMO.
Configuring EPiServer CMO after the installation
The default installation folder for the CMO Windows services is [Path to your EPiServer installation]\Shared\Services\[Name of the CMO Service]\.
Example: C:\Program Files\EPiServer\Shared\Services\CMO Aggregation Service\.
Check the logging configuration, aggregation service and thumbnail service for EPiServer CMO as follows:
- Check that the applications have required permissions to create log files in destination folders and so on. Go to the applications folder, right-click the folder, select Properties, go to the Security tab and find the account. You can add module logging settings to common CMS logging settings in the file EPiServerLog.config. See Configuring logging.
- Check that the Aggregation Service logging settings are contained in the file EPiServer.Cmo.AggregationService.exe.config in the folder where this service is installed. The CMO Admin can turn on DEBUG logging or less detailed logging for this file. See Installing and Configuring the Aggregation Service.
- Check that the Thumbnail Service logging settings are defined in the file IECaptSvc.exe.config in the folder where this service is installed.
Running EPiServer CMO and Live Monitor in a production environment
Live Monitor and CMO UI components are deployed as protected modules and by default reside inside appdata folder.
It means that these components can be deployed to production environment in the same way as the whole website. It enables running Live Monitor, CMO core and CMO UI on websites in a hosting environment where EPiServer CMS is not installed on a web server.
Note that CMO Aggregation service and Thumbnail service are deployed as windows service applications and require EPiServer CMS installed on a server.