Configuring WebDAV in Sun Java System Web Server 7.0

Configuring WebDAV in Sun Java System Web Server 7.0

Download Sun Java System Web Server 7.0 absolutely free from here .

Also check out my next blog about WebDAV Access Control Protocol(RFC 3744) support in Sun Java System Web Server 7.0.

Overview

WebDAV stands for "Web-based Distributed Authoring and Versioning". It is a set of extensions to the HTTP protocol which allows users to collaboratively edit and manage files on remote web servers. Sun Java System Web Server 7.0 conforms to WebDAV protocol as defined by the RFC 2518 and the WebDAV Access Control Protocol specification as defined by the RFC 3744.
In this article I will describe how to configure WebDAV in Sun Java System Web Server 7.0 via Administration CLI.

Steps to configure WebDAV in Sun Java System Web Server 7.0

Go to Sun Java System Web Server 7.0 installation directory.
Start Admin Server.
Start wadm.

Enabling WebDAV at instance level

magnus.conf

server.xml

default.acl

... acl "uri=/magnus-internal"; deny (all) user = "anyone"; allow (list) user = "all"; acl "dav-src"; deny (all) user = "anyone";

Adding a DAV collection

server.xml

... <dav-collection> <uri>/dav</uri> <source-uri>/source</source-uri> </dav-collection> ...

obj.conf

... NameTrans fn="ntrans-dav" name="dav" ... PathCheck fn="pcheck-dav" ... Service fn="service-dav" method="(OPTIONS|PUT|DELETE|COPY|MOVE|PROPFIND|PROPPATCH|LOCK|UNLOCK|MKCOL|ACL|REPORT)" ... <Object name="dav"> PathCheck fn="check-acl" acl="dav-src" Service fn="service-dav" method="(GET|HEAD|POST|PUT|DELETE|COPY|MOVE|PROPFIND|PROPPATCH|LOCK|UNLOCK|MKCOL|ACL|REPORT)" </Object>

Now set appropriate ACLs in default.acl or create a new ACL file for this virtual server and set ACLs in it. Make sure that the users have appropriate "rwx" permissions in docroot as required.
Note that ntrans-dav directive has to be the first Nametrans directive (before ntrans-j2ee directive) and pcheck-dav directive has to be the last PathCheck directive (after find-index-j2ee directive).

Difference Between Source Uri and Content Uri

Suppose we crate a dav-collection with content uri "/dav" and source uri as "/source".
Sending a request,
GET /dav/test.jsp HTTP/1.0
will return the output of the jsp
Hello World!!

Sending a request,
GET /source/test.jsp HTTP/1.0
will return the source of the jsp
< % System.out.println("Hello World!!"); % >

Advanced CLIs

Listing DAV collections

Normal listing

wadm>list-dav-collections --config=test --vs=test
/dav

Detailed listing

wadm>list-dav-collections --config=test --vs=test -l
uri     source-uri     enabled
------------------------------
/dav     /source     true

Setting properties at server level

wadm>set-webdav-prop --config=test max-xml-request-body-size=1024

Verify by getting the properties as shown in the next section.

Getting properties of DAV at server level

wadm>get-webdav-prop --config=test

Setting DAV Collection Properties

wadm>set-dav-collection-prop --config=test --vs=test --uri=/dav min-lock-timeout=60

Verify this by getting the properties as shown in next section

Getting properties of a DAV Collection

wadm> get-dav-collection-prop --config=test --vs=test --uri=/dav

Disabling DAV Collection

wadm>disable-dav-collection --config=test --vs=test --uri=/dav
CLI201 Command "disable-dav-collection" ran successfully

Enabling DAV Collection

wadm>enable-dav-collection --config=test --vs=test --uri=/dav
CLI201 Command "enable-dav-collection" ran successfully

Deleting a DAV collection

wadm>delete-dav-collection --config=test --vs=test --uri=/dav
CLI201 Command "delete-dav-collection" ran successfully

Disabling WebDAV at server level

wadm>disable-webdav --config=test
CLI201 Command "disable-webdav" ran successfully

Posted by meena ( May 16 2006, 11:17:56 PM IST ) Permalink Comments [0]