Friday, June 15, 2012

WebDAV Portal Urls

WebSphere portal exposes following resources over WebDav protocol -
  1. WebDAV for managing pages and static content
    1. Portal pages are represented as folders. They can contain subfolders that represent child pages.
    2. Static pages are placed in a separate folder. The content of static pages is represented as an additional folder named staticcontent.
    3. Updating metadata , globalization information
  2. WebDAV filestore. For example, this is used by mashup integration in the portal.
    1. Accessing public,users, system folders related to mashups.
  3. WebDAV for Web Content Management.
    1. Creating siteareas, components, updating the acl…etc

You can obtain the entry point URL to the WebDAV file store from the service document under the URL http://localhost:10039/wps/mycontenthandler/!ut/p/model/service-document

Different WebDAV entry points in websphere portal and WCM

  1. Entry point to access the Portal Themes


  1. Entry point to access the Portal Skins

 
 
  1. Entry point to access the Static Resources (common-resources, layouts,…etc)


  1. Entry point to access the Portal Pages  :
    1. For default portal installations

    1. For virtual portals
                                                               i.      If host name was specified when the virtual portal was created, the WebDAV URL looks like this

                                                             ii.      If the virtual portal was created with a URL context only and no host name was specified, the WebDAV URL looks like this
 
  1. Entry point to access WCM libraries
http://localhost:10039/portal_context_root/mycontenthandler/dav/content/libraries/



Using WebDAV , we can
  1. browse, changing metadata of portal pages.
  2. create, update, deletion of static pages under staticcontent. Users can access the content of static pages via the subfolder staticcontent
Using WebDAV, we can’t
  1. creating the new pages, updating the uniquename or objectid, copy or moving pages .
  2. updating portal content

WebDAV-Security

The WebDAV entry point requires user authentication via HTTP basic authentication. SSL access is not supported at this time. To use WebDAV, users log in to the portal with their portal user ID. Users can then access and work with portal pages according to their access permissions as set by Portal Access Control.

By default only administrative users can perform write operations on specific folders of the WebDAV file store. This affects public and user owned folders. You can enable write access for all authenticated users on WebDAV file stores folders.

Managing access control for theme and mashup folders:

  1. All users have view access to all resources in these folders. This includes both anonymous users and authenticated users.
  2. You can administer write access to the these folders via the virtual resource THEME MANAGEMENT provided by portal access control.
    1. To give users write access to resources contained in theme folders, for example to create, modify, or delete such resources, assign the users MANAGER role on the virtual resource THEME MANAGEMENT in portal access control.
  3. To enable write access for all authenticated users, add the following property to the WP ConfigService resource environment provider in the WebSphere Application Server administrative console: filestore.writeaccess.allowed. Set the value for the property to true .
    1. There are several WebDAV entry points. However, the property filestore.writeaccess.allowed applies to the filestore entry points for home directories for each user located at: http://server_name:WC_default_host/wps/mycontenthandler/dav/fs-type1/users/user_name
    2. Users can modify only their own directories. You must grant additional permissions for users to modify other directories.

5 comments:

  1. Hi, is there a way that we can write a document/CSS file to webdav through a portlet?

    ReplyDelete
  2. Make an HTTP connection to your WebDAV service ussing Apache HTTPClient and issue a MKCOL request (MKCOL is just like GET, POST, etc.). Something like this:

    MKCOL /the/directory/you/want/to/create HTTP/1.1

    You should expect a 201 response. If you get something else, it means that the directory creation has failed.

    ReplyDelete
  3. Hi, what is the way to connect to WPS 8.5 virtaul portal WCM libraries. I can access only libraries from base portal. But WebSphere Portal 8 and 8.5 WCM has virtaul portal specific wcm libraries. http://localhost:10039/wps/mycontenthandler/<virtual portal url context>/dav/content/libraries/ does not work :(

    ReplyDelete
    Replies
    1. because of managed-pages feature all pages in the virtual portal are copied into the Portal Site library in IBM Web Content Manager and it maintains separate wcm workspace each virtual portal.

      You can obtain the entry point URL to the WebDAV file store from the service document under the URL http://localhost:10039/wps/mycontenthandler/!ut/p/model/service-document

      Entry point to access WCM libraries
      http://localhost:10039/portal_context_root/mycontenthandler/dav/content/libraries/

      Try adding context of virtual portal and see if that helps.

      Delete
  4. Thank you for your hints!

    I did not find endpoint url for wcm libraries in scope of virtaul portal. There is only fs-type1 but no WCM libraries. I found nasty hack to use base portal libs and syndicate them to virtaul portal libs :(

    ReplyDelete