Knowledge Provider and Caching
Knowledge Provider and Caching
A cache is used to store copies of documents when they are accessed for the first time. As a result, the documents can be accessed again more quickly, since the contents are taken directly from the cache. Caching, however, must not be confused with replication (see below). With caching, the original documents are stored in one location, namely on the content server. The copies in the cache can be replaced with newer content at any time.
Documents are checked in in Walldorf. An employee in South Africa wants to access and display these documents. The transmission time, however, is extremely long and the intercontinental network connections would be overloaded. By using cache servers, the documents are only copied over the connection once.
The Knowledge Provider’s Content Management Service provides two types of caching:
Caching on special servers
Caching at the user's front end
Caching is not the same as replication.
Front-End Cache in the SAPGUI
The client cache is used by the data provider to cache documents that are read from an HTTP content server or from the SAP system.
This type of caching is extremely fast. However, each user must fill his or her own cache and resources are used at each front end.
The caching settings can be defined in the GUI options. Choose the Local Data tab and specify the directory to be used for caching as well as the maximum size of the cache files.
Cache Servers
The cache server is used to cache special content server requests. Remote accesses are cached and executed locally.
This type of caching is ideal for scenarios in which many different users have joint access to the cache. The documents only have to be sent once across the wide area network.
See also:
Cache Server