Skip to Content
This weblog explains the necessary steps to connect a KM repository from one portal to another portal via WebDAV.

We performed the following steps to connect a repository of a NetWeaver 2004s portal via WebDAV to a NetWeaver 2004 SPS 12 KM system:

  1. Creating an HTTP system for usage in the WebDAV Repository Manager

    In Content Management Configuration we navigated to Global Services -> System Landscape Definitions -> Systems -> HTTP System and created a new HTTP system.

    image

    In this case, the portals did not belong to the same user domain, therefore, a user with read permissions in the connected repository was entered. It is also possible to forward the current authentication information to the remote server. In this case, leave the user and password entry fields empty.

    The Server URL is the WebDAV URL of the repository to be connected. To get it, we displayed the details of the root folder, chose Properties and opened the tab Access Links.

    image

  2. Creating a Cache for the WebDAV Repository

    In CM Configuration we navigated to Utilities -> Caches -> Memory Cache and created a new cache.

    image

  3. Creating a WebDAV Repository Manager

    In CM Configuration we navigated to Repository Managers -> WebDAV Repository and created a new repository manager.

    image
    image

  4. Using it

    Now the new repository is available in the KM system. It can be accessed via a KM Navigation iView or assigned to an index as data source . Create a crawler to make sure the index is updated at regular intervals.

To report this post you need to login first.

7 Comments

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

  1. Fede Delgado Bellone
    Hi Sibylle,
    I’ve done exactly what you wrote, but I’ve used “Same user domain” because both of my servers are in the same domain.

    But this is not working. I’m getting the error “Object not found”. Do you have any idea what i could possibly doing wrong?

    I’ve tried entering an user with full permissions and this works perfect.

    Thanks in advance,
    Fede

    (0) 
    1. Sibylle Brehm Post author
      Hi Fede,
      Could you provide me with some more details: Does the user have access permissions to the objects in the other portal? When do you get the error message “Object not found”?
      Regards
      Sibylle
      (0) 
  2. Zigi Arielly
    Hi
    I need to have a sfdb CM repository in the internal main portal. I need that some people form the internet will connect to this repository and will see the files (including some km property that will add in the internal main portal) and will modify and add some files. I don’t want this people to enter to my internal portal, they have access to the portal in the DMZ. What you sagest?
    (0) 
    1. Sibylle Brehm Post author
      Hi,
      in this case, I would suggest to use content exchange via the ICE protocol between the two portals to distribute content from the internal portal to the portal in the DMZ. You can schedule the content exchange at regular intervals. Properties can be transported as well (except application properties).
      Regards
      Sibylle
      (0) 

Leave a Reply