Simple Web Repository Manager

Use

Like the standard Web Repository Manager, the simple Web Repository Manager allows you access to documents that are stored on remote HTTP servers. It manages all Web addresses specified in the configuration and makes them available in a single repository in the KM root directory.

Integration

To access the simple Web repository on a remote HTTP server, you specify the server URL in a Web address .

Prerequisites

The ca_websimple memory cache has been configured.

Note

SAP recommends the following cache settings, depending on the number of Web addresses used:

Recommendations for the ca_websimple cache

Number of Web Addresses	Cache Size (Max Cache Size)	Cache Capacity (Capacity)
1-5	1 MB	200
6-19	5 MB	1000
20-n	25 MB	5000

For more information, see Caches .

Features

Configuration of the simple Web Repository Manager comprises significantly fewer parameters than configuration of the standard Web Repository Manager.

Note

To be able to use more functions, you must configure a standard Web Repository Manager .

In Knowledge Management, there is exactly one simple Web Repository Manager. It is preconfigured and activated. You cannot create any further repository managers of this type.

The following parameters denote the simple Web Repository Manager:

Parameters for the simple Web Repository Manager

Parameter	Required	Description
Name	Yes	Name of the repository manager.
Description	No	Description of the repository manager.
Prefix	Yes	The URI prefix for which the manager is registered. This specification is entered in the list in the root directory. Note that the prefix must be entered with a forward slash. Default: /WWW
Active	No	The simple Web Repository Manager is activated by default. You can remove the flag to deactivate the repository manager.
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. This parameter is deactivated by default.
Send Events	No	Specifies whether the repository sends events when operations such as delete and update content are performed. This parameter is activated by default.
Cache Stale Timeout	No	Determines the time in milliseconds after which old resources are deleted from the database. The lifetime of cached resources is determined by the Cache Timeout parameter. After the timeout, they are stale. A resource older than the value in Cache Stale Timeout is removed from the cache. Default: 604800000 milliseconds (7 days)
Cache Timeout	No	Timeout in milliseconds for resources in the cache. The timeout determines the amount of time for which cached resources (content and properties) are not refreshed. The optional value is determined by the update frequency of the remote site. However, the timeout value should be shorter than the update interval of the remote location, so that the cache is updated with the latest content. For resources supplied with an "Expires" header by the remote HTTP server, the timeout is added to the expiry date. Default: 604800000 milliseconds (7 days)
HTTP Timeout	No	Timeout in milliseconds after which operations on the server are aborted. Default: 30000 ms (30 seconds)
Repository Services	No	Identifiers of the repository services that you want to use with the repository.
Memory Cache	Yes	Identifier of the memory cache to be used by the Web repository manager for caching both content and properties of generated resources. The Maximum Entry Size property in this cache determines whether the content of a resource is stored in the cache. Only resource content smaller than Maximum Entry Size is cached. In contrast, resource properties are always cached. Default: ca_websimple
Proxy System ID (Landscape Service)	No	Proxy server ID from the system landscape service (see HTTP System ) If no HTTP system is specified, the system automatically uses the default proxy system .
Persistent Caching	No	If activated, the database is used to cache objects. The database cache is used when the memory cache reaches the defined size or the maximum number of entries is reached. The maximum possible number of database cache entries is defined in the configuration of the Web garbage collector scheduler task.

Activities

To check the configuration of the simple Web Repository Manager, choose Content Management → Repository Managers → Simple Web Repository.