WebDAV

With WebDAV for HCL WebSphere Portal, use standard operating system tools to create, modify, and delete web content rather than the standard authoring portlet.

Download and install a WebDAV client, then go to...

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

For example:

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

By leveraging tools like file system explorers, WebDAV enables us to work with the web content items through familiar, everyday actions. Here are a few examples:

• We can create components or presentation templates simply by dragging a file into a corresponding folder.

• We can perform actions on several items at once. For example, we 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.

• We can modify files.

  For example, We can open a presentation template using an HTML editor, make changes to it, 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, we 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. We can also drag an existing XML file into the appropriate folder, enabling us to easily set the same data for different items.

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

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

• Content items, with the exception of managing metadata and access control
• Authoring templates, with the exception of managing metadata and access control
• Nested items within site areas
• Server-side copy and move
• Unauthenticated users
• Export 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

Lock or unlock an item through WebDAV will lock or unlock the item in WCM 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 the file is in a state that allows users to modify it, WebDAV will allow us 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 we 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, we can either rename the component itself to include the file type (for example, myImage.gif), or we 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 WCM 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 we can access the item with WebDAV.

Configure a HTTP server front end

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

See

1. WebDAV client
2. Web content items in the WebDAV tree
3. Metadata and access control for Web content items in WebDAV
4. Create taxonomies and categories with WebDAV
5. Manage content with site areas in WebDAV
6. Create components with WebDAV
7. Create presentation templates in WebDAV

Parent Develop content

Related tasks:

Work with WebDAV clients