Logical Repository

Use

In the Knowledge Provider, different repositories can be used to store document content, depending on the client in question. 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.

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

  • Clear division of documents of different clients also for storage on external content servers, in particular for

    • Application Service Providers

    • Parallel use of productive and test client(s)

  • Simplification of administration for a 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. These client-dependent repositories allow for a complete division of the content according to clients.

The logical repository was introduced to realize client-related repositories. This allows physical repositories to be accessed according to the client and the system ID.

When defining the content repository in the SAP system there is now the option to define a logical repository. A logical repository is mapped to a physical repository by means of a definition template.

The definition template contains the following variables:

  • <CLIENT> Client

  • <SYSID> System ID

When mapping the logical repository to a physical repository, the variables are replaced with real values.

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.

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.

More Information

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.