Read Access Using Distributed Cache Servers

Use

Content on the SAP Content Server can be cached.

To use the cache server, you need to make the following Customizing settings:

Locations must be defined (see Locations)
Hosts must be defined (see Hosts)
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)

The content server is accessed as follows:

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

If it was accessed from the frontend, 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.

If nothing is defined in the host table, the IP sub-networks are evaluated. 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 cannot take place.
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.