Use WebDAV with Web content

With WebDAV for WebSphere Portal, you can use standard operating system tools to create, modify, and delete Web content rather than the standard authoring portlet. Before you can use WebDAV with Web content, set up a WebDAV client. After your client is set up, you can access the Web content libraries with WebDAV using the following URL:

http://server:port/webdav/dav/content/libraries
By leveraging tools like file system explorers, WebDAV enables you to work with your Web content items through familiar, everyday actions. Here are a few examples:

In addition to modifying the actual content of an item, you can also modify any item's metadata or access control settings by modifying XML files that define the item's metadata and access control characteristics. You can also drag an existing XML file into the appropriate folder, enabling you to easily set the same data for different items.

You can create, modify, or delete the following items: libraries, taxonomies, categories, sites, site areas, components, and presentation templates.

Be aware that the following features are not supported when using WebDAV with Web content:

When using WebDAV with Web content, be aware of the following considerations.

Locked item support

Locking or unlocking an item through WebDAV will lock or unlock the item in Web Content Management and the JCR database. Because some items are represented by multiple files and folders, locking or unlocking one of these files causes locking or unlocking of the other associated files at the same time. If you lock an item, folders and files related to the content of the item, its metadata, and its access control settings are also locked.

Workflow support

There is no representation of a workflow itself in the WebDAV tree, but if a file is part of a workflow and the workflow indicates that the file is in a state that allows users to modify it, WebDAV will allow you to modify the file as well.

File names and file type suffixes

Files representing data items are always named exactly like the corresponding content item.

For example if you have an image component named myImage, the corresponding image file is also named myImage, without any suffix indicating the file type, such as .gif or .jpg.

This can sometimes cause a problem when opening the file through WebDAV because the appropriate application for editing the file cannot be chosen automatically. To account for this, you can either rename the component itself to include the file type (for example, myImage.gif), or you can manually start the editing application and open the file from within the client.

Missing items

If an item no longer displays or can no longer be modified, this could be due to a changed state for the item in the Web content server where the item is stored.

For example creating or modifying an item on the server could lead to a changed state that prevents you from accessing this item with WebDAV, depending on how workflow is set up. Expiration is another reason an item's state might change and so affect whether you can access the item with WebDAV.

Configure a HTTP server front end

When you use an HTTP server front end to work with WebDAV, you need to set Accept content for all requests to true for the Web server plugin in the administrative console under Web servers > webserver1 > Plug-in properties > Request and response.


Parent topic:

Extending Web Content Management


Related tasks


Work with WebDAV clients