Table of Contents
Advertisement
Name Translation Mapping
The HTTP server uses Name Translation mapping to translate a virtual path provided by a
gateway client to a physical path used by an HTTP server. This Name Translation mapping
specifies the gateway's HTML directory. The gateway's CGIs use this information to
output the correct URL (HTTP redirection). The NameTrans mapping is specified in the
gateway's configuration file using the
For more information on configuring the
page 97.
Gateway Root Suffix
Directory Express and the default gateway are set to the root suffix specified during
Directory Server installation. This suffix specifies the DN for the LDAP database and
represents a root in the directory tree (for example,
gateways can be set up on an HTTP server that provide access to directory entries that
correspond to this root suffix.
When the Directory Server's suffix changes, it is necessary to run the
manually to propagate the change to all gateway instances.
NOTE
When the root suffix, directory manager, or port change, the gateway
settings in
haven't been updated by Red Hat Console).
Configuring the Gateway for Web Servers
Directory Express and the default gateway are installed with the Directory Server and
configured to run under the Red Hat Administration Server, which is the default HTTP
server for the gateway clients. No additional configuration is necessary. However,
customers in high-usage networks may wish to move their gateways (or set up new
gateways) on a high-performance HTTP server.
Setting up a gateway with a web server typically requires:
Changing all the host names and port numbers in the configuration files (
1.
,
dsgw.conf
pb.conf
gwnametrans
gwnametrans
must be updated to reflect the changes (if they
dsgw.conf
,
, and so on).
default.conf
HTTP Server Configuration
parameter.
parameter, see "gwnametrans," on
dc=example,dc=com
updatedsgw
Chapter 2
Setting Up the Gateway
). Multiple
script
,
config.txt
33
Advertisement
Table of Contents
