ProcessMap

ProcessMap 2 and new versions of IE

Microsoft has locked the possibility to execut WinForms applications directly in Internet Explorer, i.e. IE Sourcing

"This is in fact a security restriction from .NET Framework 4.0 onwards, since it’s not really recommended to use .NET ActiveX controls in IE, specifically ones created with previous versions of the framework. If you need to continue using this control, you’ll need to create these registry keys (depending on the OS architecture) on all machines where the control is used."

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]
"EnableIEHosting"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework]
"EnableIEHosting"=dword:00000001

The link editor doesn’t work

When trying to create a link to a symbol the link tool opens an empty window or shows error message saying that the page could not be loaded.

Open IIS and navigate to {site}\Extensions\ProcessMapExtension. Select Compression and unselect "Enable static content compression" and save.

Logging

Logging is built in to the server parts of ProcessMap. The logging is implemented using log4net and can be activated by modifying the web.config file.
 
<configuration>
  <configSections>
    <section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler,
      log4net" />
  </configSections>
  <log4net>
    <appender name="RollingFileAppender" 
      type="log4net.Appender.RollingFileAppender">
      <file value="logs\log4net.txt" />
      <appendToFile value="true" />
      <rollingStyle value="Date" />
      <datePattern value="yyyyMMdd" />
      <maxSizeRollBackups value="10" />
      <layout type="log4net.Layout.PatternLayout">
        <conversionPattern value="%date [%thread] %-5level %logger [%property{NDC}] 
        - %message%newline" />
      </layout>
    </appender>
    <root>
      <level value="ALL" />
      <appender-ref ref="RollingFileAppender" />
    </root>
  </log4net>
</configuration>
 

Uninstallling ProcessMap

How do I uninstall ProcessMap?

First unregister everything in EPiServer:
1. Go to admin in EPiServer. Select Config/Tools Settings/Plug-in Manager. Select "ProcessMapExtension". Disable everything below the Overview-tab and save.
2. Delete all pages of template type "ProcessMap default page". Delete the template "ProcessMap default page" and delete the corresponding template file (<webroot>/templates/PageProcessMap.aspx).
3. Remove the ProcessMap property on all templates where it exist. Delete the corresponding control (ProcessMapViewer) on all template definitions (.aspx-files).
4. Go to admin in EPiServer. Select Page Type/Manage Page Types/Edit Custom Property Types. Select the ProcessMap property and delete it.

Now you cannot find any trace of ProcessMap from EPiServer's point of view.

Then delete files and folders:
1. Delete the folder <webroot>/Extensions/ProcessMapExtension.
2. Delete the following in the bin folder of the site: the files "Se.Meridium.EPiServer.Extensions.ProcessMapExtension.dll" and "FlowChart.NET.dll" an then the folders "ProcessMap.Core", "ProcessMapEditor", "ProcessMapEditor.Core" and "ProcessMapEditor.Data".
3. Delete the file <webroot>/meridiumLicense.config if ProcessMap is the only Meridium product installed. If other products exists – edit the file by removing the Licenses-tagg concerning ProcessMap.

Finally clean up web.config:
1. Remove the section tag with the name attribute "processMapExtension" below the sectionGroup tag with the name attribute  "se.meridium.epiServer.extensions".
2. Remove the add tag with the name attribute "ProcessMapExtension" below the tag httpModules.
3. Remove the "processMapExtension" tag below the tag "se.meridium.epiServer.extensions".
4. Remove the thre location tags with path attribute beginning with "Extensions/ProcessMapExtension/…".

ProcessMap and scheduled jobs

I get an exception from ProcessMap when a scheduled job is exectuted in EPiServer. What shall I do?

To deal with this problem you need a hotfix. Contact proce...@support.meridium.se.

Scheduled jobs might cause problems because ProcessMap is listening to events concerning changes in EPi pages. ProcessMap is mapping virtual paths to physical paths by using the http context. If there is no context present the physical paths to the folders where ProcessMap stores pending and published maps must be added explicitly in web.config. Add the keys "PhysicalPendingPath" and "PhysicalPublishedPath" below the processMapExtension tag. For example:

<processMapExtension>

<add key="PhysicalPendingPath" value="c:\inetpub\wwwroot\MyEPiSite\Extensions\ProcessMapExtension\
ProcessMapData\ProcessMap_pending\"/>

<add key="PhysicalPublishedPath" value="c:\inetpub\wwwroot\MyEPiSite\Extensions\ProcessMapExtension\
ProcessMapData\ProcessMap_published\"/>

</processMapExtension>

ProcessMap on EPiServer CMS R2

ProcessMap seems to work, but I get an error page when trying to open the Meridium Link Tool. Why?

In version 2.2.1 and earlier ProcessMap could not handle uiUrl on the format used in EPiServer CMS R2.
I.e. uiUrl="~/secret/UI/"

A workaround is to change this to uiUrl="http://host/secret/UI/". Remember to also change the Virtual Path Provider in the same way.
<add name="UI" virtualPath="/secret/UI/" .....