The Web Connection Managed Module is configured through settings in the Web.Config file in the root directory of your Web application.

A full Web.Config looks something like this:

<?xml version="1.0"?>
<configuration>
  <configsections>
    <section name="webConnectionConfiguration" type="System.Configuration.NameValueSectionHandler,System,Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"></section>
  </configsections>

  <system.web>
    <compilation defaultlanguage="c#" debug="false">
      <buildproviders>
        <!-- required only for Visual Studio Addin  -->
        <add extension=".wcsx" type="System.Web.Compilation.PageBuildProvider"></add>
        <add extension=".wp" type="System.Web.Compilation.PageBuildProvider"></add>
      </buildproviders>
    </compilation>
    
    <trust level="Full"></trust>
  </system.web>
<system.webserver>
    <handlers accesspolicy="Script, Execute, Read">
      <add name="*.wp_wconnect" path="*.wp" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" precondition="integratedMode,runtimeVersionv2.0"></add>
      <add name="*.wc_wconnect" path="*.wc" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" precondition="integratedMode,runtimeVersionv2.0"></add>
      <add name="*.wcsx_wconnect" path="*.wcsx" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" precondition="integratedMode,runtimeVersionv2.0"></add>
      <add name="*.wcs_wconnect" path="*.wcs" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" precondition="integratedMode,runtimeVersionv2.0"></add>
      <add name="*.wwsoap_wconnect" path="*.wwsoap" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" precondition="integratedMode,runtimeVersionv2.0"></add>      
    </handlers>
  </system.webserver>
  <webconnectionconfiguration>
    <add key="Timeout" value="60"></add>
    <add key="PollTimeout" value="100"></add>
    <add key="InputPostBufferSize" value="65356"></add>
    <add key="PostBufferLimit" value="0"></add>
    <add key="TempPath" value="c:\temp\wc\"></add>
    <add key="TempFilePrefix" value="WC_"></add>
    <add key="MessagingMechanism" value="File"></add>
    <add key="AdminAccount" value="ANY"></add>
    <add key="AdminPage" value="~/admin/admin.asp"></add>
    <add key="ExeFile" value="c:\wwapps\wc3\WebDemo.exe"></add>
    <add key="UpdateFile" value=""></add>
    <add key="LogDetail" value="False"></add>
    <add key="ValidateRequest" value="False"></add>
    <add key="ComServerProgId" value="WebDemo.WebDemoServer"></add>    
    <add key="ComServerLoadingMode" value="LoadBased"></add>
    <add key="ServerCount" value="2"></add>
    <add key="AutoStartServers" value="False"></add>
    <add key="MessageDisplayFooter" value="Error generated by Web Connection IIS Connector Module"></add>
  </webconnectionconfiguration>
  
</configuration>

configSections

Required to let ASP.NET know that there's a couple of custom configuration sections. These two sections contain the Web Connection Configuration settings and a set of error page templates.

Trust Level

The Web Connection Module performs a number of high trust operations like writing files to non-Web paths, calling COM objects, starting and stopping processes and so requires Full Trust. This is not an optional setting. Along the same lines the module requires that the app runs under LocalSystem or an Admin account.

Handler Mappings

The Handler mappings map a script map to the Web Connection module. The set up varies depending on whether IIS 10 in integrated mode or previous versions are used. You can review the specific version topics.

webConnectionConfiguration

This section contains Web Connection's main configuration settings that determine how this application operates. See webConnectionConfiguration Settings.