
You use a file system repository manager to access a directory hierarchy in a file system and make its contents available for read and write access.
Before you configure a file-system repository manager based on WINDOWS → in a portal, you have to meet certain prerequisites (see Integrating Documents from a Windows System into KM ).
If you are running a portal on UNIX, you must specify the IP addresses of the domain controller used in your Windows systems in a file and reference this in the security manager configuration (see Security Manager ).
The file system repository manager supports the following actions that can be applied to files and directories:
If you are using the repository in read-only mode, the creating, changing, renaming, and deleting of files and directories is not supported.
The following functions are not supported:
If you are using KM in a load-balancing environment, you must set up the file-system repository manager in write-protect (read-only) mode. If the repository is not read-only in such a scenario, concurrent updates to a file by different users on different installations can leave the content of the file in a corrupt state.
File System Repository Manager Parameters
|
Parameter |
Required |
Description |
|---|---|---|
|
Name |
Yes |
Name of the repository manager. |
|
Description |
No |
Description of the repository manager. |
|
Root Directory |
Yes |
This denotes the path to the root directory in the file system to which the repository manager is assigned. If you want to integrate documents from a Windows system, this can be a drive letter (followed by a colon) or directory path on the local server or a remote server share (for example, //myserver/myshare/somedir). If you are running your portal on UNIX and want to access the file system on another UNIX host, you must mount the required directory on the portal server. Example path when using a UNIX system: /usr/company/share The repository manager is responsible for the specified directory and all its subdirectories. Note that multiple repository manager configurations are not allowed to have the same subpath in their Localroot parameter. |
|
Prefix |
Yes |
The URI prefix for which the manager is registered. The URIs of all resources managed by this repository manager have this prefix in common. This prefix is used to identify the repository manager that is responsible for a resource with a given URI. Note that you must enter the prefix with a forward slash, for example, /company-share. The repository is listed under this name in the root repository of the explorer iView. |
|
Windows Landscape System |
No |
Specifies the System ID entered in the definition of a Windows system . Enter a Windows system if the repository manager accesses a Windows file system and you want to use the permissions valid there in the portal. Choose W2kSecurityManagerfor the Security Manager parameter. If you want to access the file system on another UNIX host from a UNIX portal, a Windows system is not required. |
|
Active |
No |
You can (de)activate the repository manager using the Active parameter. |
|
Hide in Root Folder |
No |
Specifies whether the repository is listed in the root directory. If you activate this parameter, the repository is not listed in the root directory. |
|
Read Only |
No |
Specifies whether the repository is read-only or not. Activate this parameter if you are operating KM in a clustered environment (see the comment above). |
|
Send Events |
No |
Specifies whether the repository sends events when operations such as delete, and update content are performed on resources. The repository sends events if this parameter is activated. This is necessary in order to use services such as the subscription service. |
|
Lookup Mode |
Yes |
Specifies the mode that a repository uses when finding resources based on their name. caseless: No distinction is made between uppercase and lowercase. exact: You have to pay attention to uppercase and lowercase in a resource name. Caseless is activated by default. |
|
Property Search Manager |
No |
Selection of the manager for the property search. Choose Standard Property Search Manager |
|
Read-Only Content Expiry Delay |
No |
Specifies how long clients are to store the content of write-protected resources. During this time, write-protected resources are not reloaded from the client to the server. This specification is in seconds. The cache options and the settings for the temporary internet files of the browser used need to be set to automatic. |
|
Repository Services |
No |
Selection of repository services that you want to use for the repository. Note that the status management service (statemngt) requires the service ACL service (svc_acl) and the application property service (properties). |
|
ACL Manager Cache |
No |
ID of the Cache for resource ACLs: ca_rsrc_acl. This parameter is required if an ACL security manager is specified in the Security Manager parameter. The cache ca_rsrc_acl is preset in the KM standard configuration. |
|
Security Manager |
No |
Selection of the security manager that controls access to repository content. To apply the permission from the WINDOWS → file system to KM, choose W2KSecurityManager. Security managers that take into account permissions between UNIX systems are not available. To be able to use permission checks within KM, choose AclSecurityManager. However, existing permissions in the source repository are not taken into account in this case. |
The file system repository /etc is already configured in the standard delivery. It contains different types of XSL stylesheets, parameter files, and other configuration files. Various CM services and repository filters need to read data from or write data to the directories of the file system repository.
The file system repository manager references a share on the portal server. This central share must be specified via the Root Directory parameter of the file system repository manager. By default, this parameter is preconfigured and its value is <servletpath >/etc .
\usr\sap\<SID>\<Java_instance_name>\SYS\global\config\cm\etc
Specifics of the File System Repository Manager in a Clustered Environment:
In a clustered environment the Root Directory parameter of each server node must point to a central share in a file system. Depending on the type of the clustered environment, ensure the following:
The Root Directory parameter of the different server nodes must not point to different physical shares. There is no synchronization mechanism between different server nodes if the file system repository of each server node points to a specific physical share.
SAP recommends that you set all static resources (GIF files, Java scripts, and stylesheets) in the /etc repository to write-protected. In the configuration of the repository /etc, the parameter Read-Only Content Expiry Delay should have the value 600 seconds.
To create and configure a file system repository manager, choose Content Management → Repository Managers → File System Repository.
See also:
Integrating Documents from a Windows System into KM
Follow-On Activities
To be able to start a search in this repository, you must assign an index to the repository (see Assigning Data Sources ). If an index has not yet been created, you must create an index now. For more information, see Creating an Index .
Example configuration of a UNIX file system repository manager:
Name = fs_rep_unixLocalroot = /usr/company/sharePrefix = /company-share-unixRead Only = deactivatedSend Events = activatedRepository Services = properties, ratingACL Manager Cache = ca_rsrc_aclSecurity Manager = AclSecurityManager
Example configuration of a WINDOWS → file system repository manager:
Name = fs_rep_windowsLocalroot = //myserver/myshare/somedirPrefix = /company-share-windowsRead Only = deactivatedSend Events = activatedRepository Services = properties, ratingACL Manager Cache = ca_rsrc_aclSecurity Manager = W2KSecurityManager