Architecture

The figure below illustrates the deployment of the cache for the POWL enabling service and is followed by an explanation:

The user operates in front of the browser and sends his http request to the Gateway server.

The Gateway server in turn forwards the request using RFC to the Gateway OData Channel which resides in the back end.

The cache for OData services is called. It builds the cache key (hash code) using the information supplied by the Gateway (such as selection criteria and navigation path). It then looks up the cache for that key. If the data is found it is returned to the Gateway.

If no data is found in the cache, the call is delegated to the data provider of the service (here the POWL–OData enabling service) which has been specified in Customizing.

If the data is found it is returned to the Gateway. At the same time it is added to the cache.