HTTP Server ConfigurationChapter 2 Setting Up the Gateway 33Name Translation MappingThe HTTP server uses Name Translation mapping to translate a virtual path provided by agateway client to a physical path used by an HTTP server. This Name Translation mappingspecifies the gateway’s HTML directory. The gateway’s CGIs use this information tooutput the correct URL (HTTP redirection). The NameTrans mapping is specified in thegateway’s configuration file using the gwnametrans parameter.For more information on configuring the gwnametrans parameter, see “gwnametrans,” onpage 97.Gateway Root SuffixDirectory Express and the default gateway are set to the root suffix specified duringDirectory Server installation. This suffix specifies the DN for the LDAP database andrepresents a root in the directory tree (for example, dc=example,dc=com). Multiplegateways can be set up on an HTTP server that provide access to directory entries thatcorrespond to this root suffix.When the Directory Server’s suffix changes, it is necessary to run the updatedsgw scriptmanually to propagate the change to all gateway instances.Configuring the Gateway for Web ServersDirectory Express and the default gateway are installed with the Directory Server andconfigured to run under the Red Hat Administration Server, which is the default HTTPserver for the gateway clients. No additional configuration is necessary. However,customers in high-usage networks may wish to move their gateways (or set up newgateways) on a high-performance HTTP server.Setting up a gateway with a web server typically requires:1. Changing all the host names and port numbers in the configuration files (config.txt,dsgw.conf, pb.conf, default.conf, and so on).NOTE When the root suffix, directory manager, or port change, the gatewaysettings in dsgw.conf must be updated to reflect the changes (if theyhaven’t been updated by Red Hat Console).
