Steps to configure IIS to serve Alcea from a subdirectory:
Our example assumes that requests to http://IISHOST/ is the IIS server, and http://IISHOST/test/ will be forwarded to the Alcea server running on the same machine… IIS and Alcea are already installed and running.
Although it is possible to rename “test”, currently there is a maximum length for this alias of 4 characters and we recommend you get things working before attempting to change it.
- asp (download link, .zip) should be placed in a directory all by itself. We will assume that it is placed in “C:AlceaASP” Control Panel, Administrative Tools, Internet Services Manager.
- Under “Default Web Site”, right-click, choose “New -> Virtual Directory”A Wizard starts: For Alias, enter “test”
- For Directory, we will use the directory that Default.asp is installed: C:AlceaASP
- Ensure that “Read” and “Run scripts (such as ASP)” are checked.
- >Now we right-click our virtual directory, and choose “Properties”
- We choose the Custom Errors tab, and for http errors “404” and “405”, choose Message Type: “URL”, and in the URL field, enter: “/test/default.asp”.
We now have IIS configured correctly – we must finally configure Alcea so that it will rewrite it’s urls to support this setup…
- Connect directly to Alcea (not through IIS), and login as an administrator
- Choose “Admin Menu”, “Customize Strings”Edit “sURLPREFIX”…
- Set it to “/test/” (without the quotes, but with both slashes).
- If you are using https, change sURLPREFIX to your complete url (https://server/) so that notification links contain the correct address.
Note: The easiest way to set sURLPREFIX is to manually set it in the server.cfg and then restart the system. A setting there will override the LANG-lang.cfg string settings of all the different tracks and allow you to control in one place. It is also easier to do it here if using the DB module, since editing the DB is harder than a file.
The format in server.cfg would be :
The format in the LANG-lang.cfg files would be :
Access to Alcea should now be possible either directly, or through IIS.
Additionally, one user noticed that when running Alcea as a service, “I changed the Log On for the service to Local System Account and everything appears to work properly now.”
– Recent versions of IIS require you to turn on the ASP functionality. If you have problems, please test with a simple helloWorld.asp file first and make sure that works.
– IIS treats errors from local address differently unless you specify otherwise.
The “Edit Feature Settings” option to the right of the Error Page settings. Set to custom or it will not work properly when testing on a local machine. If you are getting a login page with messed up images, try requesting an image directly from the local machine which may give you a better error message.
If you have questions or problems, please contact Alcea support: firstname.lastname@example.org
– IIS Defaults (allow attachments)
IIS installs with a number of defaults which limit the size of requests to the server. Large requests and attachments will be limited to 200k unless you make a few modifications :
1- Double-click Request filtering, edit feature settings. Set Maximum allowed content length to 2000000000
2- Double-click ASP, expand Limit Properties. Set Maximum Requesting Entiry Body Limit and Response Buffering Limit to 2000000000
3- For large responses: click on Default Web Site (I think this needs to be set at the root level for some reason), double-click ASP, expand Limit Properties and raise the “Response Buffering Limit”. This is needed when returning a large amount of data (e.g., a SOAP filter returning lots of data).