Manually setup Dovetail WebServices on Windows 2003 Server
We had a customer who needs to be able to manually setup our WebServices under IIS6 so I thought it would be best to share this with everyone.
This guide will take you through setting up a virtual web directory under IIS version 6 on Windows Server 2003. It will also show you how to set the security on your files to make sure the web service will work.
- You will need to have Dovetail SDK installed on the target machine.
Note: The installer can automatically setup WebServices. The goal of this post is to outline the manually steps that will reproduce what the installer does automatically. - You will also need to have the web application role setup on the Windows 2003 server.
- Bring up IIS Manager.
- Right click on Default Web Site
- Click on New and select the Virtual Directory… task
- Fill in the Alias
- Point it at the WebServices Assemblies
- Make sure you select Read and Run Scripts
- Complete the wizard and the Virtual Directory will be created.
- Next you need to make sure that the user the web service is running under will have write access to the fc_cache directory.
- Right click on fc_cache
- Select the Security tab
- Edit the security settings such that the user account that the web server is running as has Modify rights. The user account you will need to assign Modify rights will depend how your organization does security. It will likely be Network Services or IUSER_MACHINENAME.
By default, IIS is configured to use pass-through authentication for Basic and Kerberos authentication when working in a Windows Server 2003 environment and running application pools with the Network Services identity. You can also configure Windows Server 2003 so pass-through authentication is possible for any authentication method. – TechNet article
- Edit the security settings such that the user account that the web server is running as has Modify rights. The user account you will need to assign Modify rights will depend how your organization does security. It will likely be Network Services or IUSER_MACHINENAME.
- You will need to make sure the web.config has your database connection settings.
- Give it a Shot: http://localhost/FChoice.WebServices.Clarify/
- To make sure that everything is working click on ClarifyApplicationSvr.asmx which will initialize the application.
Hopefully I didn’t miss anything.
