WebDAV | HCL Digital Experience

With WebDAV for HCL Digital Experience, you can use standard operating system tools to create, modify, and delete web content rather than the standard authoring portlet.

Before you begin

Before you can use WebDAV with web content, you need to set up a WebDAV client. After your client is set up, you can access the web content libraries with WebDAV with the following URL:

http://server:port/portal_context_root/mycontenthandler/dav/content/libraries/

For example:

http://www.example.com:10027/wps/mycontenthandler/dav/content/libraries/

About this task

By using tools like file system explorers, WebDAV is used to work with your web content items through familiar, everyday actions. Here are a few examples:

You can create components or presentation templates by dragging a file into a corresponding folder.
You can run actions on several items at the same time. For example, you can create five images at the same time by dragging five image files into the image component folder. This creates five separate image components, and for each image component the file name is used for the component's name and title.
Modifying items is also straightforward through a WebDAV client. For example, you can open a presentation template by using your preferred HTML editor, make changes, and then save the changes. The WebDAV client takes care of accessing the web content library, downloading the template, and then uploading the changes.

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, site areas, folders, components, and presentation templates.

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

Content items, except for managing metadata and access control
Authoring templates, except for managing metadata and access control
Nested items within site areas
Server-side copy and move
Unauthenticated users
Exporting of web content libraries with WebDAV to be imported into another web content server

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

Locked item support: Locking or unlocking an item through WebDAV locks or unlocks the item in Web Content Manager 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 that are 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 that is 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.
Configuring 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 WebSphere® Integrated Solutions Console under Web servers > webserver1 > Plug-in properties > Request and response.