Running The Gateway In High-Usage Networks; Http Server Configuration; Name Translation Mapping; Gateway Root Suffix - Netscape DIRECTORY SERVER 6.2 - GATEWAY CUSTOMIZATION Manual

Running the Gateway in High-Usage Networks

Network administrators expecting high gateway usage may wish to move the
gateway to a high-performance HTTP server that is dedicated to running the
gateway.
NOTE

HTTP Server Configuration

The following sections describe the steps for configuring an HTTP server:
•

Name Translation Mapping

•

Gateway Root Suffix

• Configuring the Gateway for Web Servers
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
gwnametrans
For more information on configuring the
"gwnametrans" on page 84.
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,
dc=example,dc=com
provide access to directory entries that correspond to this root suffix.
If you do decide to migrate the gateway's configuration files to a
high-performance HTTP server, we recommend you use Netscape
Enterprise Server.
parameter.
). Multiple gateways can be set up on an HTTP server that
parameter, see
gwnametrans
Chapter 2 Setting Up the Gateway
HTTP Server Configuration
27