Content Server Aliases
Content server aliases can be used from release 4.6B and from Knowledge Warehouse 4.5.
Before release 6.10, the URL for accessing a content server is set independently of the client location. However, in complex environments, especially in connection with firewalls, it may be necessary to involve the client when accessing various servers. For example, a content server can be accessed from several different locations via the same firewall.
A similar situation occurs when a distributed repository system, such as an archive, consists of a number of servers all at different locations, all of which can facilitate access to the entire repository system.
Therefore, when the URL is retrieved, it is possible to change the entries for server, port, and script, independently of the location. For example, the entry for the original server could be replaced by an entry for the content server alias.
A content server alias can be, for example, an IP filter on a firewall that forwards the requests unchanged to the content server.
Cascaded Caching and Content Server Aliases
You can use caches and content server aliases (see also Content Server Alias) in combination with each other. If you are using a combination, the system first looks for an alias. If the system finds an alias, the technical data of the cache server is used instead of the technical data of the content server. This means that the location of the server has changed. This information is then taken into account when the cache server is being located.
For details of the required Customizing steps and a description of the individual activities, see the Implementation Guide (IMG) under the following path:
· SAP Web Application Server → Basis Services → Knowledge Provider → Content Management Service → Distribution → Define Content Server Alias
and
· Define Location Path for Multi-Layer Caching
See also: