ibm websphere portal blog,websphere portal, portal blog, ibm blog,websphere blog,websphere tips and tricks, websphere interview questions, portal interview questions, portal faqs

WebSphere Portal 8 WEB-DAV features | IBM WebSphere Portal Blog

Pages

Wednesday, October 8, 2014

WebSphere Portal 8 WEB-DAV features

WebSphere Portal 8 WEB-DAV features

 

Web DAV support is introduced in the IBM websphere portal from  v6.1 onwards , but in v7.x it can provide a lot of different things like below
  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 

Note: 
a. To download theme as zip file
http://localhost:10039/wps/mycontenthandler/dav/themelist/<theme_dir>?mime-type=application/zip

b. To upload zip file to WebDAV
./ConfigEngine.sh webdav-deploy-zip-file -DTargetURI=dav:fs-type1/iwidgets/myWidget/ -DZipFilePath=/tmp/myWidget.zip
  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/
Folder Structure looks like
libraries
   - wcm.library.my_library
       - authoringTemplates
       - components
       - presentationTemplates
       - sites
       - taxonomies
   - wcm.library.contentlibrary
       - components
       - presentationTemplates
       - sites
       - taxonomies
 
Note: “/all” at end of URL is temporary fix who are using 7.0.0.0 (without any cumuliative fix)

Folder structure and reserved folder names under fs-type1

The fs-type1 WebDAV entry points provide the following set of predefined root folders used by the Page Builder theme:
  • themes
  • skins
  • layout-templates
  • common-resources
  • iwidgets
The fs-type1 WebDAV entry points provide the following set of predefined root folders used by mashup integration:
  • public
  • users
  • system
Note:
  1. None of these folders can be deleted, not even by an administrator
  2. Folder and file structure is only simulated and is not a real file system structure.
  3. The properties files are only simulated. They contain parameters and their values. You cannot save any additional information, for example comments.
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