Logical Repository (SAP Library - Knowledge Provider (BC-SRV-KPR))

Logical Repository

Purpose

In the Knowledge Provider, different repositories can be used to store document content, depending on the client in question. This type of repository is known as a client-specific repository. Client-specific repositories allow content to be separated according to client, including when external content servers are used.

The benefits of client-specific HTTP repositories are as follows:

Client-specific repositories allow content to be separated according to client, including in cases where external content servers are used. This is particularly useful for application service provider enterprises, and in cases where live and test clients and running in parallel.
Client-specific repositories also greatly simplify the administration of your system landscape.

Features

Previously, client-specific content storage was only possible in the Online Transaction Processing (OLTP) database. The functionality has been introduced to Knowledge Provider in response to customer demand, especially from Application Service Providers.

The concept of the logical repository is central to implementing client-specific repositories. It is the logical repository that makes it possible to access different physical repositories by means of the client and the system ID.

Note

Logical repositories are maintained in transaction OAC0.

You define the logical repository along with the content repository in the SAP system. A definition template is used to map the logical repository to a physical repository.

The definition template can contain the following values:

<CLIENT> Client

<SYSID> System ID

This graphic is explained in the accompanying text

These variables are replaced by concrete values during the actual mapping process.

Example

In client 001 of the SAP system ABC, the definition template <SYSID>_CONTENT_<CLIENT> is mapped to the physical repository ABC_CONTENT_001.

In client 002 of the same system (ABC), the definition template is mapped to the physical repository ABC_CONTENT_002.

In client 001 of the SAP system DEF, the same definition template is mapped to DEF_CONTENT_001.

In client 003 of system DEF, the same definition template is mapped to DEF_CONTENT_003.

This graphic is explained in the accompanying text

You can now use the SYSID to centrally administrate the assignment of repositories in several SAP systems and to distribute the assignments to other systems. The various systems can then use different repositories.

Other Notes

Ideally, you need an SAP system of release 6.10, or at least 4.6C. Any required modifications are provided by means of Support Packages.