Skip to Content

This part of KM trasnport deals with WebDav Methodology of transporting KM content. These series of weblogs exclusively discussed about KM transports.To have a look at them and my all other weblogs, please click here. 

WebDav methodology of KM transport  for content is the final weblog in these KM Transports weblog series. In the past 5 parts, we saw exlclusively a strategy devised for KM transport. KM transport occurs in two parts, config and content. Both of them has to be transported seperately. We saw the config transport in KM transports: Part II and KM transports: Part III. We saw that content transport for KM can be done in two methodologies namely ICE and WebDav. We saw ICE methodology of KM Content transport in KM transports: Part IV and KM Transports: Part  V. Now lets discuss about webdav transport methodology.

WebDav ( as I previously said ) stands for Web-based Distributed Authoring and Versioning. Its actually a global concept which we would comfortably try using in this scenario. Generally it is used to work on servers and files and folders which are physically remote . A typical example would be FTP access in internet. You actually work on the remote folders and files in a windows explorer view.

By the way, have you ever wondered where would the documents and folders of KM repository be in the portal server ? I have always been in my early days. When I explored the URL, thats when i found out there is another intuitive way of transporting content for KM. The WebDav method. As result of my search i found out that the KM docs get stored at seprate place in the portal server which can be accessed by an URL. The URL pattern would be, http(s)://00/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs. Then you would get a screen asking to open the KM contents either by navigation user interface or web folder method. Refer screenshot below,

image

Select web folder method. Then you would see all your KM contents being displayed in a windows explorer view like below,

image

Now you can play around with these folders and documents just like how you deal with windows folders. Basically this utility will be more useful when you have to upload bulk documents into KM. But you can also do transports between landscapes too. Just open the web folder views for both the landscapes. Then copy the folder or documents from the source system and paste it over the destination system. Remember in the first part I said I have a seperate inclination to this methodology, I have a strong hunch that you too feel it that way now.

Anyways KM transport blog series has come to an end. I will talk to you guys in another interesting topic in a short while. Below is the link for accessing all of my weblogs,

My weblogs list 

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Bhaskar B
    Hi,

    Nice series of weblogs, thanks for the info. It will be a nice piece of information for newbies. Old wine in a new bottle.

    Sorry, WEBDAV is not a KM transport tool. You can view/upload/dload with that. Better than WEBDAV, Portal drive is also very useful tool available since SP 14.

    Only ICE can retain the properties between the environments.

    Great work man,
    keep going

    (0) 
    1. Anonymous
      1) How is a protocol that allows you to upload/download “not” a transport tool?

      2) Portal Drive is a client. WebDAV is a protocol. Portal Drive uses WebDAV.

      3) WebDAV allows you to get and send properties (except application properties for now), so it can be used (and is used) for transporting properties as well.

      Best regards, Julian

      (0) 
      1. Gopal Krishnan Post author
        Thank you so much you both guys in commenting about my blogs. There has been a long time I waited for someone give me a feed back. Now,

        1. Baskar, I dont know if WebDav is an accepted transport standard through industries, but I use it every now and then where I dont have to worry much about permissions or configurations. Regarding your ideas about Portal drives, I would say webdav and portal drive are one and the same work environment

        2. Julian, thanks for your views. I firmly accept with you that webdav and portal drive are one and the same work environment. Julian I dont have any comments about you saying WebDav would retain all properties. Because I have not retained some properties like layout when I do transports. But permissions were retained.

        (0) 
      2. Gopal Krishnan Post author
        About these points,

        1) How is a protocol that allows you to upload/download “not” a transport tool?

        I would categarize webdav as a transport tool and Im more fond of using it rather than using ICE, because of the ease of use

        2) Portal Drive is a client. WebDAV is a protocol. Portal Drive uses WebDAV.

        Yes, I would agree with this too

        3) WebDAV allows you to get and send properties (except application properties for now), so it can be used (and is used) for transporting properties as well.

        I havent made enough research about this yet. So Im not gonna say anything about it. I was ablte to see all the properties except for layout. The layout wasnt transported. Let me do more explorations.

        (0) 

Leave a Reply