Show TOC

 Integrating Documents from a Windows System into KMLocate this document in the navigation structure

Purpose

You want to integrate documents that are stored on a Windows operating system into Knowledge Management. The documents in question can be stored on a remote system or actually on the portal server.

If you want to use permissions, the following variants are possible:

  • Variant 1

    When accessing the documents using SAP Enterprise Portal, the same permissions should be valid for users as on the Windows operating system of the documents that you want to integrate into KM (that is, read, write, or delete permissions). The W2K security manager is used for this.

  • Variant 2

    When accessing documents in the portal, the permissions set in KM are valid.

The variant you can use in your system landscape depends on the operating system you are using to run the portal. If you are using Microsoft Active Directory Service, you may not be able to use variant 1. Check the prerequisites below.

 

Prerequisites

General Prerequisites

  • You have installed an operating system in version Windows Server 2003, Windows XP, or Windows 2000 on the system where the documents that you want to integrate are stored.
  • A Windows System has been created in the CM system landscape and in the portal system landscape (see Creating a System in the Portal System Landscape ).

 

Additional Prerequisite if Using the Portal on WINDOWS

 

Additional Prerequisite if Using the Portal on UNIX or Linux

  • You have specified the IP addresses of the domain controllers that manage the domains of the users that access repository content with permissions in a file. This file is referenced in the configuration of the security manager for Windows (see Security Managers ).
  • For variant 1: If you are using Microsoft Active Directory Service, you have to operate the Windows domain in mixed mode.

     

Restrictions

  • Windows NT 4 Service Pack 5 is only supported if the operating system on which the portal is running is a Windows operating system. Documents from a Windows NT 4 system cannot be integrated into a UNIX/Linux portal.
  • The table below contains an overview of the possible variants you can use if you are using Microsoft Active Directory Service:

Overview of the Configuration When Using Microsoft Active Directory Service (Domain Is Run in Mixed Mode)

  Network Path Configuration 
  "Use jCIFS" deactivated(for access from Windows portal to Windows systems)  "Use jCIFS" activated(for access from UNIX/Linux portal to Windows systems)

File system mount service active

Mount possible (variant 2)

Mount possible (variant 2)

W2K security manager

Variant 1 can be used, Windows permissions are valid in the portal

Variant 1 can be used, Windows permissions are valid in the portal

Overview of the Configuration When Using Microsoft Active Directory Service (Domain Is Run in Native Mode)

  Network Path Configuration 
  "Use jCIFS" deactivated(for access from Windows portal to Windows systems)  "Use jCIFS" activated(for access from UNIX/Linux portal to Windows systems)

File system mount service active

Mount possible (variant 2)

Mount possible (variant 2)

W2K security manager

Variant 1 can be used, Windows permissions are valid in the portal

Variant 1 cannot be used - separate permissions must be set in KM

If you use the Microsoft Active Directory Service, the following combinations are possible.

Process Flow

Carry out the following steps for both variants:

 

Note

The steps are specified for a Windows 2000 system. Operating-system-specific specifications such as paths and names of settings may differ with other Windows operating systems.

  1. Share the required directory in the Windows file system.

    Open the Windows Explorer and choose the directory that you want to release. Click with the secondary mouse button and choose Sharing.

    From the Sharing tab, choose Share This Folder. Click Permissions, and add a user with administrator rights to the list.

    Give the user all permissions for accessing the directory.

    If necessary, you can release the directory for all users and define the permissions for the folder.

    Confirm your entries and close the dialog box.

 

  1. Configure a Network Paths .

    This step is necessary if you want to access a remote system. Enter the path to the released directory.

    If you want to access a WINDOWS system from a UNIX/Linux system, activate the Use jCIFSparameter.

 

  1. Now create a File System Repository Manager .

    Enter the System ID of the Windows system into Windows Landscape System.

    Enter the previously defined network path (Network Path) in Root Directory. If your documents are stored on the portal server, enter the relevant disk and directory, for example, C:\data.

    For variant 1: In Security Manager, choose W2kSecurityManager.

    Note

    You should note that when using the portal on UNIX/Linux, you must store a file in the configuration of this security manager that contains the domain information for all WINDOWS remote servers (see Security Managers ).

    For variant 2: In Security Manager, choose AclSecurityManager.

     

  2. Carry out user mapping for the Windows system in the portal (see Specifying User Mapping ).
    Note

    Enter the Windows user and domain in user mapping (in the form DOMAIN\USER).

 

Result

If you have carried out all the steps, you can now access documents and folders in the configured repository. Every time a document is accessed, the system checks whether the user has the necessary permissions.

System Principals are excluded by the check. Whether you have further access to documents depends on your permissions.