Siebel Server Sync Guide > Configuring Siebel Server Sync >
Configuring the IIS Web Server for Exchange
SSSE has certain configuration requirements for the Internet Information Services (IIS) Web server where the Exchange Server resides. This topic describes how to meet those requirements.
This task is a step in Process of Configuring SSSE.
The Siebel Exchange Connector uses the WWW Distributed Authoring and Versioning (WebDAV) extension to HTTP to perform calendar operations. The Secure Socket Layer protocol (SSL, which uses URLs that start with https:) is not supported. If the Web Server for Exchange is set up to require authentication, then you must either set up the Exchange Connector application to run using the security context of a user that the Web Server authentication will accept as valid, or else reconfigure the Web Server to allow anonymous access.
If you have the urlscan product installed, make sure that the urlscan.ini file (typically located at
C:\WINNT\system32\inetsrv\urlscan\urlscan.ini) is set up to allow the following:
- Make sure that urlscan allows for the following verbs:
- Make sure the Web server allows the HTTP request header Translate.
- If you want SSSE to synchronize Outlook-created calendar items that contain periods in the Subject field, then make sure AllowDotInPath is set to 1. This directs the Web server to accept URLs that contain periods in them. This setting is relevant because SSSE uses WebDAV to interact with Exchange Calendar records. This kind of interaction requires WebDAV to specify a URL that includes a file name that is based on the text of the Subject for the calendar item.
- Make sure that [DenyUrlSequences] is configured appropriately for your requirements. For example, if you want to allow Outlook-created items with ".." in the Subject, you must comment out the ".." line in the urlscan.ini file. You can comment out a line in the file by placing a semi-colon (;) at the beginning of the line.
- If Web server logging options are turned on, log files are typically located in
C:\WINNT\system32\inetsrv\urlscan\logs. When the Web server rejects a URL because it does not meet the criteria specified in the .ini file, Exchange Connector log files record the rejected URL. You can use the URL from the Connector log file to find entries in the Web server log file that will help you to determine why the URL was rejected. For example, the following error indicates that urlscan is configured to reject PROPPATCH requests:
[06-03-2004 - 17:31:36] Client at 172.20.63.233: Sent verb 'PROPPATCH', which is not specifically allowed. Request will be rejected.
The following error indicates that urlscan is configured to reject the Translate request header:
[06-03-2004 - 23:20:45] Client at 172.20.63.221: URL contains disallowed header 'translate:' Request will be rejected. Site Instance='1', Raw URL='/exchange/pimsi2202/Calendar/WzkBF100800142102ibndtst81.eml'
NOTE: Note the URL contains the user ID which may be useful for debugging purposes.