Weblog
17/2: Setting up Domino to work with IIS
For companies that use Windows and IE, IIS simplifies the authentication of web users with integrated Windows authentication. When integrated with Domino, this means that web users do not need a separate web password. This clearly has big administration advantages.Unfortunately, the instructions in the help have been plagued with mistakes both at version 5 and version 6.x. I wanted to post some instructions here that correct those mistakes and make it easier for others. If there are any mistakes here then please let me know!
When upgrading a domino server from version 5 to version 6 (or 7), there is a big change in the way the integration works. At version 5, IIS served the web pages and you didn't require the HTTP process to be loaded within Domino. At version 6, both IIS and Domino serve web pages and there is a plugin required for IIS so that it knows which URLs to send across to Domino and which to serve itself. For example, you would want any URLs containing ".NSF" to be passed to Domino but any containing ".ASP" would need to be served by the IIS server.
If the two servers are running on the same box, the two HTTP processes must be configured to use different port numbers. Usually the default port 80 would be assigned to the IIS server and another port chosen for the Domino HTTP task. If IIS and Domino are on different servers then you can choose to keep the ports the same if you wish.
Here is the official Lotus help with errors fixed.
[Update 6th May 2006: Another useful document here describes how HTTP threads are queued by the HTTP task in Domino (changed between versions 5 and 6) and the new NOTES.INI setting at version 6.5.5 that enables you to change it.]
