Googled "iSeries WebDav" and got this hit for V5R3:
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/r
zaie/rzaieconfigwebdav.htm
Set up WebDAV for HTTP Server (powered by Apache)
This topic provides information about how to set up WebDAV for your HTTP
Server with the IBM(r) Web Administration for iSeries(tm) interface.
Important: Information for this topic supports the latest PTF levels for
HTTP Server for iSeries . It is recommended that you install the latest
PTFs to upgrade to the latest level of the HTTP Server for iSeries. Some
of the topics documented here are not available prior to this update.
See
http://www.ibm.com/servers/eserver/iseries/software/http/services/servic
e.htm for more information.
Web-based distributed authoring and versioning (WebDAV) is a set of
extensions to the HTTP protocol that allows WebDAV clients (such as
Microsoft(r) Web Folders) to collaboratively edit and manage files on
remote Web servers. See WebDAV for HTTP Server (powered by Apache) for
more information.
To configure WebDAV on your server, do the following:
Click the Manage tab.
Click the HTTP Servers subtab.
Select your HTTP Server (powered by Apache) from the Server list.
Select Global configuration from the Server area list.
Expand Server Properties.
Click Request Processing.
Click the WebDAV tab in the form.
Specify one of the following under WebDAV lock databases:
Full path name for locking stream files: - the full path of the DAV lock
database for the Root (/) or QOpenSys streaming file system.
Library/name for locking QSYS objects: - the library and file name of
the DAV lock database for QSYS objects.
Click OK.
Select the context you want to work with from the Server area list. The
server area you select will be WebDAV enabled.
Click Request Processing.
Click the WebDAV tab in the form.
Select Enabled to Enable WebDAV.
Enter the appropriate file system under Repository provider.
Enter any WebDAV restrictions you want enabled for this server area.
Click OK.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Dixon
Sent: Monday, October 27, 2008 6:25 AM
To: Midrange Systems Technical Discussion
Subject: Mapping Network drives with Vista - possible clues to problems.
I reported under another thread that I could map a network drive from
Vista to V5R3 but not to V5R1 and from the responses that I received it
seemed that no one could map to V5R1 using Vista. I have been looking
further into the problems and thought it made sense to start a new
thread.
Firstly, I have since found that, whilst I could map a network drive to
V5R3 internally, I could not do this remotely. So I used a network
protocol analyser (wireshark) to look at the traffic and found that
Vista handled remote and internal network drives very differently. The
reason that the remote network drive did not work was because Vista used
HTTP for mapping the external drive and found that under V5R3 I had not
authorised PROPFIND, hardly surprising because I had never heard of it.
It is part of WEBDAV about which I also know nothing. Does anyone else
have problems mapping a network drive remotely from Vista to V5R3? Has
anyone got this to work?
Secondly, and as a result, I checked remotely using Vista to V5R1 and
found that my V5R1 box sent back a message saying that PROPFIND had not
been implemented, presumably because under V5R1 I am using the old HTTP
server rather than Appache. Has anyone one tried mapping a drive from
Vista remotely to a box that uses Appache under V5R1? It is possible
that, in this case, they would get the not authorised rather than the
not implemented message.
Network protocols are outside my comfort zone, and, as I am about to go
away for a few days, I thought that I would pass on what I have
discovered, because someone who knows more than me might say that I have
misunderstood or someone else might tell me how to authorise PROPFIND.
I have yet to try mapping from Vista to an internal V5R1 system when
using the protocol analyser.
--
Rob Dixon
www.erros.co.uk
www.boarstall.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
