This document describes how to install and configure Microsoft IIS for E-WMS ASP on Windows 10, for release 410 and earlier.
For configuration in Windows 10 for release 411 and later, please see this document.
In IIS, usage of non-default .NET usage or for instance usage of a 32bit application, is managed through IIS 'Application pools'. Application pools are also used to isolate web applications. In release 410 and earlier, E-WMS ASP is a 32-bit web application, and requires .NET framework 3.5. Therefore it is required to link an application pool with specific settings.
In the IIS manager, expand the server name. Right click on "Application Pools" and select Add Application Pool. Name the Application Pool, for instance WMS.
E-WMS (410 and earlier) requires following configuration:
Press OK to save this new Application Pool.
For release 410 and earlier and in 64-bit Windows, it is necessary to define a specific setting, which is only available in the Application Pool settings.
Start the IIS manager and expand the server name. Click on "Application Pools", a list with available Application Pools will show. Select the pool you want to use for E-WMS and then press right click, Advanced Settings. On a 64 bit server, change the setting "Enable 32-bit Applications" to True and press OK. Also make sure 'Managed Pipeline Mode' is set to 'Classic'.
When a specific Application Pool was configured for E-WMS, it still has to be linked to the E-WMS web site.
In IIS manager, expand the server name, expand "Sites", expand "Default web site". Click on the E-WMS web site and choose Basic settings in the far right panel. Click on Select and choose the specific Application Pool which was created in the previous step: Press OK to save this configuration.
You can test the basic workings of the new web site by clicking on the web site name 'wms' and then choosing 'Browse *:80 (http)' in the far right panel.
Microsoft Edge (or your default browser) will then be started with the website http://localhost/wms.
If you see one of these pages, then the WMS website is working OK:
For known IIS error messages, see these documents.