November Happy Hour will be moved to Thursday December 5th.
November Happy Hour will be moved to Thursday December 5th.
Product version: |
Live Monitor 2.0 |
---|---|
Document version: |
1.0 |
Document last saved: |
This document provides installation instructions and troubleshooting information regarding the Live Monitor module. For further configuration and system description refer to the document Configuration - Live Monitor.
NOTE: If you plan to use Live Monitor on an EPiServer CMS 6 Demo Site, it is recommended to install the demo site first, before installing Live Monitor. The installation order for the modules are described below.
Download and unzip the Live Monitor.zip file onto your computer and run the Live Monitor.msi file.
Sart the EPiServer Deployment Center. The EPiServer Deployment Center can be found in the EPiServer folder on the start menu
Live Monitor relies on WCF services for communication between the silverlight client and the server. This in turn adds some configuration requirements when using multiple site bindings (e.g. http://mysite.com & https://mysite.com). The most stright-forward option for fixing this is configuring "base address prefix filters":
<configuration>
<system.serviceModel>
<serviceHostingEnvironment ...>
<baseAddressPrefixFilters>
<!-- this is the address from which I want to run the live
monitor client -->
<add prefix="http://mysite.com"/>
</baseAddressPrefixFilters>
</serviceHostingEnvironment>
</system.serviceModel>
</configuration>
The symptom for this problem is that no trace information is logged, and no visitors are shown in the client. Code blocks prevents the live monitor tracking web control from beeing added at the end of the form tag. The most stright-forward option for fixing this is manually adding the epitrace tracking web control to the master page:
<%@ Register TagPrefix="epitrace"
Namespace="EPiServer.Trace.CMS.Web.WebControls"
Assembly="EPiServer.Trace.CMS" %>
<html><body>
<form runat="server">
<% // My nasty code block and other markup %>
</form>
<epitrace:VisitTracker TrackingHandlerUrl="~/TrackerHandler.ashx" runat="server"/>
</body></html>
Also disable the page plugin in admin mode: Admin > Config > Plug-in Manager > Live Monitor > Overview.
When installing with Deployment Center uncheck "Database tables" and manually run [Program Files]\EPiServer\CMS\[Version]\Modules\EPiTrace\epitraceHits.ora with SQLPlus.exe connected to your existing <EPiServer Oracle User>.
When installing Live Monitor on an EPiServer CMS 6 demo site, it is recommended to install the modules in the following order:
Open web.config set bindingConfiguration of the TraceService endpoint to a binding with the security mode set to "transport", e.g.:
<system.serviceModel>
<services>
<service behaviorConfiguration="EPiServer.Trace.Services.TraceServiceBehavior" name="EPiServer.Trace.CMS.Services.TraceService">
<endpoint bindingConfiguration="basicHttpBinding" .../>
</service>
</services>
<bindings>
<basicHttpBinding>
<binding name="basicHttpBinding">
<security mode="Transport" />
</binding>
</basicHttpBinding>
</bindings>