Getting Live Monitor to work with CMO

This topic describes several installation and upgrading scenarios for the Episerver Live Monitor add-on. Version 7.17 (released February 2015) of Live Monitor (LIMO) is based on HTML5, and you can integrate it with Episerver CMO. 

Background

From version 7.17 and higher, Episerver Live Monitor is installed as a NuGet package in Visual Studio. Earlier versions (former EpiTrace) where installed as .msi files from Episerver Deployment Center (DC). From version 7.5.446, you can install EpiTrace/Live Monitor using NuGet. 

Having CMO previously installed (via Deployment Center) will not affect the Live Monitor upgrading process. If you want to use CMO with the Live Monitor, you need to install CMO from Deployment Center, together with a CMS 7.5 site.

Upgrading scenarios

SCENARIO 1: Installing Live Monitor from scratch

  • Install Episerver CMS using the Visual Studio extension.
  • [optional] Update the NuGet packages.
  • Install the EPiServer.LiveMonitor NuGet package.
  • Configure OWINStartup.

SCENARIO 2: Existing CMS 7.5 site with Live Monitor installed from Deployment Center

Options to upgrade:

  1. Update to the latest version of EPiServer.Packaging.
  2. Update to EPiServer.LiveMonitor.7.5.446.2 and then to the latest version of EPiServer.LiveMonitor,
    OR, updating directly to the latest version of EPiServer.LiveMonitor. Both alternatives are described below.

Site status before upgrading:

  • A LiveMonitor folder is placed in appdata/Modules (no entry in appdata/Modules/packages.config), there is nothing related to LiveMonitor in the folders ModulesRepository, modules and modulesbin.
  • The following  files are in the bin folder:
    • EPiServer.Trace.CMS.dll
    • EPiServer.Trace.dll
    • EPiServer.Trace.UI.dll

STEP 1. Update to latest version of EPiServer.Packaging.

Site status after this step:

  • The three .dll files listed above remain in the bin folder.
  • The appdata/ModulesRepository and modulesbin folders are empty.
  • The LiveMonitor folder is in the folder modules/_protected (unzipped).

STEP 2, Option A: Upgrade through NuGet to EPiServer.LiveMonitor.7.5.446.2 first, and then the latest version.

  1. Run Install-Package EPiServer.LiveMonitor -version 7.5.446.2 in the Package Manager console.
  2. Upgrade to the latest version of EPiServer.LiveMonitor. When updating EPiServer.LiveMonitor from 7.5.446.2 to the latest version for the "AlloyMvc" project, the error message appears: Could not load file or assembly EPiServer.Trace.UI or one of its dependencies. The system cannot find the file specified.

    Do the following to resolve this issue:
    1. Delete the content in the modules/_protected/LiveMonitor folder.
    2. Configure OWINStartup.
    3. Optionally delete the following section in web.config):
      <dependentAssembly>
      <assemblyIdentity name="EPiServer.Trace.Cms" publicKeyToken="8fe83dea738b45b7" culture="neutral" />
      <bindingRedirect oldVersion="0.0.0.0-7.5.446.0" newVersion="7.5.446.0" />
      </dependentAssembly>
      <dependentAssembly>
      <assemblyIdentity name="EPiServer.Trace" publicKeyToken="8fe83dea738b45b7" culture="neutral" />
      <bindingRedirect oldVersion="0.0.0.0-7.5.446.0" newVersion="7.5.446.0" />
      </dependentAssembly>
      <dependentAssembly>
      <assemblyIdentity name="EPiServer.Trace.UI" publicKeyToken="8fe83dea738b45b7" culture="neutral" />
      <bindingRedirect oldVersion="0.0.0.0-7.5.446.0" newVersion="7.5.446.0" />
      </dependentAssembly>

STEP 2, Option B: Upgrade through NuGet directly to the latest version of EPiServer.LiveMonitor.

  1. Upgrade to the latest version of EPiServer.LiveMonitor.
  2. Configure OWINStartup.
    After this step, both old EPiServer.Trace and the new EPiServer.LiveMonitor in the global navigation are in edit view. Do the following to resolve this issue:
  3. Delete the content in the modules/_protected/LiveMonitor folder.
  4. Delete the following files from the bin folder:
    • EPiServer.Trace.CMS.dll
    • EPiServer.Trace.dll
    • EPiServer.Trace.UI.dll

SCENARIO 3: Existing CMS Site 7.5 with LiveMonitor 7.5.446.2 from NuGet

Steps to upgrade:

  1. Update the CMS site to EPiServer.Packaging 3.2 or later.
  2. Run Install-Package EPiServer.LiveMonitor -version 7.5.446.2 in the Package Manager console (adds EPiServer.LiveMonitor 7.5.446.2 to AlloyMvc).
  3. Run Update-Package EPiServer.LiveMonitor in the Package Manager console (updates LiveMonitor in AlloyMvc).
  4. Configure OWINStartup
  5. Optionally delete the following section in web.config:
    <dependentAssembly>
    <assemblyIdentity name="EPiServer.Trace.Cms" publicKeyToken="8fe83dea738b45b7" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-7.5.446.0" newVersion="7.5.446.0" />
    </dependentAssembly>
    <dependentAssembly>
    <assemblyIdentity name="EPiServer.Trace" publicKeyToken="8fe83dea738b45b7" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-7.5.446.0" newVersion="7.5.446.0" />
    </dependentAssembly>
    <dependentAssembly>
    <assemblyIdentity name="EPiServer.Trace.UI" publicKeyToken="8fe83dea738b45b7" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-7.5.446.0" newVersion="7.5.446.0" />
    </dependentAssembly>

Last updated: Feb 12, 2015