Upgrading to Internet Information Services 7 (IIS7)

Effective 11/14/08, the AbleCommerce 7.0.1 release will install using IIS7 application server. If you are running AbleCommerce 7.0.1 (released on 11/14/08) you do not need to make the changes shown in this document.

If you installed AbleCommerce version 7.0.0, released before 11/14/08, and have upgraded to version 7.0.1 or higher, you can modify the web.config file as shown below. These changes will allow you to upgrade and use Microsoft's Internet Information Service, version 7.

File to Modify

/web.config (in the root folder)

To Implement Compatibility with IIS7.0 Integrated Pipeline Mode:

If you want to use IIS7, without setting the application pool to "classic ASP.NET", then after upgrading, you will need to manually change the web.config file.

Open the web.config file in the root of the AbleCommerce installation and locate the system.webServer section toward the bottom.

The default installation will contain this data:

To upgrade, new nodes must be added. This is the default data from a 7.0.1 installation. As you can see, the AbleCommerce Http Module is added, along with three additional handlers.

Take special care when you copy the text below as you may end up with extra line breaks which should be removed after pasting them.

        <system.webServer>
         <validation validateIntegratedModeConfiguration="false"/>
         <modules>
                 <add name="ScriptModule" preCondition="integratedMode" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                 <add name="AbleCommerceHttpModule" type="CommerceBuilder.Services.AbleCommerceHttpModule, CommerceBuilder.Services" preCondition="managedHandler" />
         </modules>
         <handlers>
                 <remove name="WebServiceHandlerFactory-Integrated"/>
                 <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral,   PublicKeyToken=31bf3856ad364e35"/>
                 <add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral,   PublicKeyToken=31bf3856ad364e35"/>
                 <add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd"   type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
                 <add name="WebChart.axd_GET" path="WebChart.axd" verb="GET" type="WebChart.CachedImageService, WebChart" preCondition="integratedMode,runtimeVersionv2.0" />
                 <add name="Captcha.ashx_*" path="Captcha.ashx" verb="*" type="CommerceBuilder.Web.CaptchaGenerator, CommerceBuilder.Web" preCondition="integratedMode,runtimeVersionv2.0" />
                 <add name="ProcessPayPal.ashx_*" path="ProcessPayPal.ashx" verb="*" type="CommerceBuilder.Payments.Providers.PayPal.IpnProcessor, CommerceBuilder.Paypal" preCondition="integratedMode,runtimeVersionv2.0" />
         </handlers>
</system.webServer>

Upgrading to Internet Information Services 7 (IIS7)

To Implement Compatibility with IIS7.0 Integrated Pipeline Mode: If you want to use IIS7, without setting the application pool to "classic ASP.NET", then after upgrading, you will need to manually change the web.config file.

To Implement Compatibility with IIS7.0 Integrated Pipeline Mode:

If you want to use IIS7, without setting the application pool to "classic ASP.NET", then after upgrading, you will need to manually change the web.config file.