Reading via Distributed Cache Servers (SAP Library - Knowledge Provider (BC-SRV-KPR))

Reading via Distributed Cache Servers

Purpose

The contents on the SAP Content Server can be cached.

To be able to use cache servers, you must define the following Customizing settings:

Locations must be defined (see Locations)

The hosts must be defined (see Hosts)

The caches must be defined (see Caches)

Set/get parameter LCA (transaction SU3)

Note

If possible, use the other transactions to choose the procedure. Do not choose the procedure using the set/get parameters.

IP subnets must be defined (see IP Subnets)

Prerequisites

A cache server is installaed on your computer (see SAP Content Server Installation Guide).

Process Flow

The content server is accessed as follows:

The access location (LU = location of user) is determined.

If access is made via the front end, the parameter LCA is evaluated. If no values have been specified for the LCA parameter, the host table is evaluated. If the host table has not been maintained, the IP subnets are evaluated.

With access via the back end, the location of the application server is determined. First, the host table is evaluated. If the host table has not been maintained, the IP subnets are evaluated. If no value is found, the "empty" location is used.

The location of the content server (LC) is determined.

First, the host table is evaluated. If the host table has not been maintained, the IP subnets are evaluated.

If LU = LC, access is provided directly.

Caching is not carried out.

The caches at the location LU are determined from the host table.

If one cache is found, access takes place via this cache.

If more than one cache is found, the load is automatically distributed among them.