Create WebDAV virtual folder in IIS pointing to AxCMSWebDav directory of your CMS installation. Do not create WebDAV virtual

Transcription

1 AxCMS.net and WebDAV WebDAV installation Create WebDAV virtual folder in IIS pointing to AxCMSWebDav directory of your CMS installation. Do not create WebDAV virtual folder under existing CMS web sites or virtual folders. Set following properties for this virtual folder: Add wildcard application mapping to aspnet_isapi.dll In IIS5, click Configuration - Mappings - Add. Set Executable path to C:\WINDOWS\Microsoft.NET\Framework\v \aspnet_isapi.dll and Extension to.*. Check All verbs and uncheck Check that file exists In IIS6, click Configuration - Mappings - Insert. Set Executable path to C:\WINDOWS\Microsoft.NET\Framework\v \aspnet_isapi.dll and uncheck Verify that file exists. In IIS7, set your application pool to Classic.NET AppPool (or other application pool with classic managed pipeline mode), then in Handler Mappings, Add Script Map, with Request path '*' and executable C:\WINDOWS\Microsoft.NET\Framework\v \aspnet_isapi.dll. In Request Restriction, Make sure "Invoke handler..." is unchecked and All verbs is selected on Verbs tab. Set proper access permissions Go to Directory Security - Authentication and access control - Edit If you plan to use AxCMS.net authentication for WebDAV, check Enable anonymous access and uncheck all other authentication methods. Make sure anonymous access settings have the correct account assigned and Allow IIS to control password checked. If you plan to use Active Directory authentication for WebDAV check Integrated Windows authentication and uncheck all other authentication methods and Enable anonymous access. If you use IIS6, enable WebDAV in the IIS Manager (node Web Service Extensions) - this is needed so IIS responds to queries with complete set of webdav commands. On IIS7, this option is located in WebDAV Authoring Rules, and there Enable WebDAV. Go to AxCMSWebDav directory of your AxCMS.net installation and create web.config configuration file with at least following contents (see an example web.config file below): <appsettings> section <add key="dbconnstring" value="server=(local);database=axcms;uid=axinomcms;pwd=axinomcms1" Put connection string to your AxCMS.net database here. Use the same value as in AxCMSWeb web.config. <add key="davapplicationurl" value=" Put URL to WebDAV virtual folder you created. URL should not end with / and should not be localhost Since AxCMS.net 8.0, you should use another property: <add key="davapplicationvirtualpath" value="/axcmswebdav" Then you can use WebDav with any host header. <add key="mediaserverrootdir" value="c:\projects\axcms\axcmsweb" Put full path to AxCMSweb folder. Use the same value as in AxCMSWeb web.config. <add key="cmssystemrootdir" value="c:\projects\axcms\axcmsweb" Put the physical path to the AxCMS.net-installation directory. Use the same value as in AxCMSWeb web.config. <add key="cmsapplicationvirtualpath" value="/axcmsweb" Put the full virtual path to the AxCMS.net-application (if any). Use the same value as in AxCMSWeb web.config.

2 <system.web> section If you plan to use AxCMS.net authentication for WebDAV, add following: <authentication mode="none"></authentication If you plan to use Active Directory authentication for WebDAV, add following: <authentication mode="windows"></authentication> If you plan to use Active Directory authentication for WebDAV, set AxCMSWeb to use active directory and import active directory users to AxCMS.net users. Make sure users who may access WebDAV have a role to pass WebDavAccess checkpoint. Make sure users have appropriate rights and roles for other WebDAV checkpoints. Open Windows Explorer and try to open your WebDAV installation using UNC path, like \\webdavserver\webdavpath\. If you are using Active Directory authentication for WebDAV and logged in into the same active directory, no password will be asked. If you are not logged into active directory, enter your active directory username like DOMAIN\username and password. If you are using AxCMS.net authentication for WebDAV, enter AxCMS\username and password. How to setup WebDAV in a productive environment In the productive environment you normally cannot create a virtual folder directly. You have to create a virtual site first. Unfortunately you cannot place WebDAV virtual folder under the CMS virtual site. Windows Explorer seems to connect and to authenticate itself to the host part of a WebDAV URL. The Forms authentication of a CMS web application will confuse it. To install WebDAV on a productive environment do exactly the following: Create a new empty directory AxCMSWebDAV_Dummy. Don't place any sensitive data in it. Create a new virtual site with the home directory AxCMSWebDAV_Dummy. It should use some url other than your CMS url as host header. Allow anonymous authentication and disable all other authentication methods for that site. Leave the default ASP.NET application created for you by the wizard, but make sure you have no execute permissions for it (Execute Permissions: None). If your CMS is based on ASP.NET 0, switch the version in the ASP tab to the 0 version and put the application into the application pool for Framework 0 applications. Add a virtual folder under that virtual site pointing to a AxCMSWebDAV directory with the AxCMSWebDAV application. Note: the AxCMSWebDAV directory must not be under AxCMSWebDAV_Dummy on the harddrive Configure this virtual folder as described above. Note that most probably trying to open the WebDAV folder configured this way from the same computer will not work. Use other computer as client or set up your WebDAV folder in Default Web Site. WebDAV installation troubleshooting Follow the next steps to find out the reason of the problem: Try to open WebDAV with usual browser by opening WebDAV URL, like If the CMS WebDAV application is normally functioning, you should get XML document with properties of the URL. If you can get the XML, but you cannot access the share in Windows Explorer, most probably you've misconfigured the virtual site in the productive environment (see "How to setup WebDAV in a productive environment" above). Check exceptions in you exceptionmanagment, you might have misconfigured paths to the system. Try to monitor HTTP traffic between WebDAV client and WebDAV server. Check the requests of the client and responses of the server.

3 Don't forget you have to login as AxCMS\<username>, not just as <username>. Do not rely on error messages returned by Windows Explorer or "net use" command. They are always misleading. Again, see the point Make sure WebClient service is running on your client computer - it is required for Windows explorer to connect to webdav. For Windows XP x64 and Windows 2003 you may need to install the Web Extender Client component - see this KB article. 7. Try to restart client computer to restart the web client service and its connection to Windows Explorer. Try to open another webdav location to let Windows Explorer know about web client service. Known limitations of WebDAV clients WebDAV cannot be run as a separate website. There are problems with interpreting separate WebDAV websites by Windows Explorer. When WebDAV virtual folder is located under the site other than Default Web Site, it will not open from the same computer. This is the problem of Windows Explorer. Categories containing any of these symbols - \ / : *? " < > - prohibited file name symbols in Windows, will not display and function correctly. Windows Vista has problems opening Page shortcuts from WebDAV folder. You can map your WebDAV folder as network drive as a workaround for this bug. When deleting file or folder, even if error occurred and the item is not deleted, Windows Explorer removes it from the list. After refresh it shows the item again, but doesn't allow any actions with it until the folder structure is completely refreshed. These applications are known to have problems working with WebDAV in AxCMS.net: PhotoShop AutoCAD Web.Config Example <?xml version="0" encoding="utf-8"?> <configuration> <configsections> <section name="exceptionmanagement" type="microsoft.applicationblocks.exceptionmanagement.exceptionmanagersectionhandler, Microsoft.ApplicationBlocks.ExceptionManagement" </configsections> <exceptionmanagement> <publisher mode="on" assembly="axinom.framework" type="axinom.framework.exception.exceptionpublisherfile" File="D:\Inetpub\MyApplicationFolder\WebDAV_exception.txt" </exceptionmanagement>

4 <appsettings> <add key="dbconnstring" value="server=(local);database=axcms_mydb;uid=myusername;pwd=mypassword" <add key="davapplicationvirtualpath" value="/axcmswebdav" <add key="mediaserverrootdir" value="c:\projects\axcms\axcmsweb" <add key="cmsinstancename" value="entwicklungs-cms" <add key="encryptpasswordsms" value="0" <add key="isaxcms" value="1" <add key="cmsapplicationhostname" value=" <add key="cmssystemrootdir" value="c:\projects\axcms" <add key="cmsapplicationvirtualpath" value="/axcmsweb" <add key="cmsextension" value=".axcms" <add key="publishdirectory" value="/publish" </appsettings> <system.web> <compilation defaultlanguage="c#" debug="true" <customerrors mode="off" <authentication mode="none" <trace enabled="false" requestlimit="10" pageoutput="false" tracemode="sortbytime" localonly="true" <sessionstate mode="inproc" cookieless="false" timeout="20" <globalization

5 requestencoding="utf-8" responseencoding="utf-8" <httpruntime executiontimeout="60000" maxrequestlength="500000" </system.web> </configuration>